Date: Mon, 4 Dec 2023 19:59:44 +0100 From: Kurt Jaeger <pi@freebsd.org> To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Cc: stable@freebsd.org Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs Message-ID: <ZW4hoJEr1hayauMn@fc.opsec.eu> In-Reply-To: <20231204230246.f11fce2914500a99e094de0b@dec.sakura.ne.jp> References: <20231201031737.DF0231B942@freefall.freebsd.org> <ZWsI4SbNU2xPjaPF@marvin.hueftgold.tld> <ZW2P8xz046Eqo_0u@fc.opsec.eu> <445y1eaxiz.fsf@be-well.ilk.org> <20231204230246.f11fce2914500a99e094de0b@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > On Mon, 04 Dec 2023 08:48:52 -0500 > Lowell Gilbert <freebsd-stable-local@be-well.ilk.org> wrote: > > > Kurt Jaeger <pi@freebsd.org> 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 ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZW4hoJEr1hayauMn>