From nobody Mon May 20 21:26:41 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VjrHH3Y0Vz5LVhS for ; Mon, 20 May 2024 21:26:51 +0000 (UTC) (envelope-from saper@saper.info) Received: from q.saper.info (q.saper.info [IPv6:2605:2700:0:2:a800:ff:fec7:5c61]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "q.saper.info", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VjrHF6CDSz4WxY for ; Mon, 20 May 2024 21:26:49 +0000 (UTC) (envelope-from saper@saper.info) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=saper.info header.s=Sep2014 header.b=JGRAIcE8; dmarc=none; spf=none (mx1.freebsd.org: domain of saper@saper.info has no SPF policy when checking 2605:2700:0:2:a800:ff:fec7:5c61) smtp.mailfrom=saper@saper.info Received: from q.saper.info (localhost [127.0.0.1]) by q.saper.info (8.18.1/8.18.1) with ESMTPS id 44KLQflQ005384 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 20 May 2024 21:26:41 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1716240401; bh=aMrLdKWLb1RMaNKDzAN5KokvNHiKuOV4g4KhuCxgfC4=; h=Date:From:To:Subject; b=JGRAIcE8z/6nTYLvz7DSCS5iLXhPi6yPl+zsVhqboCjPGaea8pr23pDVsMzAxiRmi rAMno2Er86t2A387xYG5GshWpkTb3DwzmYUs3HNkl39S7x/2wabc3aw9Tu5n+8GPDG uOdba/b7yjUS2sp95XyTdC5pOCIhgcvgp1OUrKvU= Received: from localhost (saper@localhost) by q.saper.info (8.18.1/8.18.1/Submit) with ESMTP id 44KLQf67005381 for ; Mon, 20 May 2024 21:26:41 GMT (envelope-from saper@saper.info) X-Authentication-Warning: q.saper.info: saper owned process doing -bs Date: Mon, 20 May 2024 21:26:41 +0000 From: Marcin Cieslak To: current@FreeBSD.org Subject: __memcpy_chk family of functions Message-ID: <20qspnq2-8qp0-pq49-rq65-986n0q4r6rqq@fncre.vasb> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.27 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.972]; R_DKIM_ALLOW(-0.20)[saper.info:s=Sep2014]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[saper.info]; RCPT_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:47066, ipnet:2605:2700::/32, country:US]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[current@FreeBSD.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_XAW(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; DKIM_TRACE(0.00)[saper.info:+] X-Rspamd-Queue-Id: 4VjrHF6CDSz4WxY Hello, I have updated some binary packages using pkg(8) but neglected to rebuild the world and my favourite web browsers no longer started complaining about the undefined symbol __memcpy_chk@FBSD_1.8 Would that be a good idea to add that information to the Handbook and possible bump FreeBSD_version and add this info to UPDATING? I fully accept that running -CURRENT as a daily driver leads to surprises like this, but it took me a bit long to figure out which change has caused this [1]. I was also thinking, would that be ok to add the synopsis of _memcpy_chk and other functions to the relevant memcpy(3) etc. manpages? Only when viewing the diff I found out I could learn about those from ssp(3). Thanks for keeping FreeBSD alive, Marcin [1] spoiler alert: https://reviews.freebsd.org/D32306