From nobody Mon Dec 4 18:59:44 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 4SkXz94zGSz52h2L for ; Mon, 4 Dec 2023 18:59:49 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (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 4SkXz91G3Yz3VPM for ; Mon, 4 Dec 2023 18:59:49 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from pi by fc.opsec.eu with local (Exim 4.97 (FreeBSD)) (envelope-from ) id 1rAEAS-00000000MSL-0Jxf; Mon, 04 Dec 2023 19:59:44 +0100 Date: Mon, 4 Dec 2023 19:59:44 +0100 From: Kurt Jaeger To: Tomoaki AOKI Cc: stable@freebsd.org Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs Message-ID: References: <20231201031737.DF0231B942@freefall.freebsd.org> <445y1eaxiz.fsf@be-well.ilk.org> <20231204230246.f11fce2914500a99e094de0b@dec.sakura.ne.jp> 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-Disposition: inline In-Reply-To: <20231204230246.f11fce2914500a99e094de0b@dec.sakura.ne.jp> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-Rspamd-Queue-Id: 4SkXz91G3Yz3VPM Hi! > 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. I'm fine with a little confusion if there's less churn during updates. > 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. It happens not very much, so it really does not matter. A note in the EN would be sufficient from my point of view. -- pi@FreeBSD.org +49 171 3101372 Now what ?