Date: Mon, 4 Dec 2023 09:51:39 -0800 From: Xin LI <delphij@gmail.com> To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Cc: stable@freebsd.org Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs Message-ID: <CAGMYy3vF6h=4ZM5tBFUzNk3TX83cP5j_MiRsF6J3bm6%2BWPfS8w@mail.gmail.com> 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
--000000000000d0b9b4060bb2c5c8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Dec 4, 2023 at 8:32=E2=80=AFAM Tomoaki AOKI <junchoon@dec.sakura.ne= .jp> wrote: > 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. > > 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. Part of this is because freebsd-update generally wants to exclude cosmetic changes (like build timestamps, etc., which does not have an effect on runtime behavior) in binary patches, so in order to "fix" this we would need to change the update builder, at the expense of always delivering a kernel change regardless if there are any real changes to the binary. At the time when I owned the builder code, the consensus was that we are moving to a packaged base really soon (tm) and the builder is in "maintenance mode" so we didn't invest a lot in this front. Cheers, --000000000000d0b9b4060bb2c5c8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon= t-family:monospace,monospace"><br></div></div><br><div class=3D"gmail_quote= "><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Dec 4, 2023 at 8:32=E2=80= =AFAM Tomoaki AOKI <<a href=3D"mailto:junchoon@dec.sakura.ne.jp">junchoo= n@dec.sakura.ne.jp</a>> wrote:<br></div><blockquote class=3D"gmail_quote= " style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);= padding-left:1ex">On Mon, 04 Dec 2023 08:48:52 -0500<br> Lowell Gilbert <<a href=3D"mailto:freebsd-stable-local@be-well.ilk.org" = target=3D"_blank">freebsd-stable-local@be-well.ilk.org</a>> wrote:<br> <br> > Kurt Jaeger <<a href=3D"mailto:pi@freebsd.org" target=3D"_blank">pi= @freebsd.org</a>> writes:<br> > <br> > > I had thought that the ZFS fix is a kernel fix so that the kernel= <br> > > would also report -p1, but it does not. It might be because<br> > > zfs is a kernel module, so the kernel itself was not really patch= ed,<br> > > but I might be wrong here.<br> > <br> > As far as I can see, that seems exactly right.<br> <br> As this kind of confusion caused by mismatch of patchlevel between<br> kernel and userland arises from time to time, now would be the time to<br> switch to keep patchlevel in sync between kernel and userland.<br> <br> This would force both kernel and userland to be built using the same<br> patchlevel, even if one of which is actually unchanged.<br> But maybe helpful to avoid confusion like this.<br> <br> What was worse this time was that a non-in-kernel-but-in-tree module,<br> zfs.ko, is updated but kernel itself is not updated.</blockquote><div><br><= /div><div class=3D"gmail_default" style=3D"font-family:monospace,monospace"= >Part of this is because freebsd-update generally wants to exclude cosmetic= changes (like build timestamps, etc., which does not have an effect on run= time behavior) in binary patches, so in order to "fix" this we wo= uld need to change the update builder, at the expense of always delivering = a kernel change regardless if there are any real changes to the binary.=C2= =A0 At the time when I owned the builder code, the consensus=C2=A0was that = we are moving to a packaged base really soon (tm) and the builder is in &qu= ot;maintenance mode" so we didn't invest a lot in this front.</div= ><div class=3D"gmail_default" style=3D"font-family:monospace,monospace"><br= ></div><div class=3D"gmail_default" style=3D"font-family:monospace,monospac= e">Cheers,</div></div></div> --000000000000d0b9b4060bb2c5c8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGMYy3vF6h=4ZM5tBFUzNk3TX83cP5j_MiRsF6J3bm6%2BWPfS8w>