From nobody Mon Dec 4 14:02:46 2023 X-Original-To: stable@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 4SkQNf00G1z53PFP for ; Mon, 4 Dec 2023 14:02:58 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SkQNc0w5Bz4kJK for ; Mon, 4 Dec 2023 14:02:55 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp; dmarc=none Received: from kalamity.joker.local (123-1-22-158.area1b.commufa.jp [123.1.22.158]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 3B4E2kxf010856 for ; Mon, 4 Dec 2023 23:02:47 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 4 Dec 2023 23:02:46 +0900 From: Tomoaki AOKI To: stable@freebsd.org Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs Message-Id: <20231204230246.f11fce2914500a99e094de0b@dec.sakura.ne.jp> In-Reply-To: <445y1eaxiz.fsf@be-well.ilk.org> References: <20231201031737.DF0231B942@freefall.freebsd.org> <445y1eaxiz.fsf@be-well.ilk.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-0.69 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.996]; MV_CASE(0.50)[]; NEURAL_HAM_SHORT(-0.19)[-0.190]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[stable@freebsd.org]; R_DKIM_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SkQNc0w5Bz4kJK X-Spamd-Bar: / On Mon, 04 Dec 2023 08:48:52 -0500 Lowell Gilbert wrote: > Kurt Jaeger writes: > > > I had thought that the ZFS fix is a kernel fix so that the kernel > > would also report -p1, but it does not. It might be because > > zfs is a kernel module, so the kernel itself was not really patched, > > but I might be wrong here. > > As far as I can see, that seems exactly right. As this kind of confusion caused by mismatch of patchlevel between kernel and userland arises from time to time, now would be the time to switch to keep patchlevel in sync between kernel and userland. This would force both kernel and userland to be built using the same patchlevel, even if one of which is actually unchanged. But maybe helpful to avoid confusion like this. What was worse this time was that a non-in-kernel-but-in-tree module, zfs.ko, is updated but kernel itself is not updated. -- Tomoaki AOKI