Re: February 2024 stabilization week
Am 2024-02-24 21:18, schrieb Konstantin Belousov: On Fri, Feb 23, 2024 at 08:34:21PM -0800, Gleb Smirnoff wrote: Hi FreeBSD/main users, the February 2024 stabilization week started with 03cc3489a02d that was tagged as main-stabweek-2024-Feb. At the moment of the tag creation we already knew about several regression caused by libc/libsys split. In the stabilization branch stabweek-2024-Feb we accumulated following cherry-picks from FreeBSD/main: 1) closefrom() syscall was failing unless you have COMPAT_FREEBSD12 in kernel 99ea67573164637d633e8051eb0a5d52f1f9488e eb90239d08863bcff3cf82a556ad9d89776cdf3f 2) nextboot -k broken on ZFS 3aefe6759669bbadeb1a24a8956bf222ce279c68 0c3ade2cf13df1ed5cd9db4081137ec90fcd19d0 3) libsys links to libc baa7d0741b9a2117410d558c6715906980723eed 4) sleep(3) no longer being a pthread cancellation point 7d233b2220cd3d23c028bdac7eb3b6b7b2025125 We are aware of two regressions still unresolved: 1) libsys/rtld breaks bind 9.18 / mysql / java / ... https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277222 Konstantin, can you please check me? Is this the same issue fixed by baa7d0741b9a2117410d558c6715906980723eed or a different one? Most likely. Since no useful diagnostic was provided, I cannot confirm. It is. And for the curious reader: this affected a world which was build with WITH_BIND_NOW (ports build with RELRO and BIND_NOW were unaffected, as long as the basesystem was not build with BIND_NOW). Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF signature.asc Description: OpenPGP digital signature
Re: February 2024 stabilization week
On Fri, Feb 23, 2024 at 08:34:21PM -0800, Gleb Smirnoff wrote: > Hi FreeBSD/main users, > > the February 2024 stabilization week started with 03cc3489a02d that was tagged > as main-stabweek-2024-Feb. At the moment of the tag creation we already knew > about several regression caused by libc/libsys split. > > In the stabilization branch stabweek-2024-Feb we accumulated following > cherry-picks > from FreeBSD/main: > > 1) closefrom() syscall was failing unless you have COMPAT_FREEBSD12 in kernel >99ea67573164637d633e8051eb0a5d52f1f9488e >eb90239d08863bcff3cf82a556ad9d89776cdf3f > 2) nextboot -k broken on ZFS >3aefe6759669bbadeb1a24a8956bf222ce279c68 >0c3ade2cf13df1ed5cd9db4081137ec90fcd19d0 > 3) libsys links to libc >baa7d0741b9a2117410d558c6715906980723eed > 4) sleep(3) no longer being a pthread cancellation point >7d233b2220cd3d23c028bdac7eb3b6b7b2025125 > > We are aware of two regressions still unresolved: > > 1) libsys/rtld breaks bind 9.18 / mysql / java / ... >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277222 > >Konstantin, can you please check me? Is this the same issue fixed by >baa7d0741b9a2117410d558c6715906980723eed or a different one? Most likely. Since no useful diagnostic was provided, I cannot confirm. > > 2) panic: ... - wait_fw_init - mlx5_load_one >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277211 > > Hopefully they would be fixed before March stabweek. > > We closed the stabilization period on Thursday. > > If you want to reap the fruits of the stabweek and you are very conservative > and want to use only changes that passed certain level of testing, you can use > the stabweek-2024-Feb branch. The branch is published at > https://github.com/glebius/FreeBSD/tree/stabweek-2024-Feb. > > Otherwise I would recommend to use 7d233b2220cd3d23c028bdac7eb3b6b7b2025125 of > FreeBSD/main as a good point to update. We did not observe any large or risky > changes in main during the week. > > -- > Gleb Smirnoff
February 2024 stabilization week
Hi FreeBSD/main users, the February 2024 stabilization week started with 03cc3489a02d that was tagged as main-stabweek-2024-Feb. At the moment of the tag creation we already knew about several regression caused by libc/libsys split. In the stabilization branch stabweek-2024-Feb we accumulated following cherry-picks from FreeBSD/main: 1) closefrom() syscall was failing unless you have COMPAT_FREEBSD12 in kernel 99ea67573164637d633e8051eb0a5d52f1f9488e eb90239d08863bcff3cf82a556ad9d89776cdf3f 2) nextboot -k broken on ZFS 3aefe6759669bbadeb1a24a8956bf222ce279c68 0c3ade2cf13df1ed5cd9db4081137ec90fcd19d0 3) libsys links to libc baa7d0741b9a2117410d558c6715906980723eed 4) sleep(3) no longer being a pthread cancellation point 7d233b2220cd3d23c028bdac7eb3b6b7b2025125 We are aware of two regressions still unresolved: 1) libsys/rtld breaks bind 9.18 / mysql / java / ... https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277222 Konstantin, can you please check me? Is this the same issue fixed by baa7d0741b9a2117410d558c6715906980723eed or a different one? 2) panic: ... - wait_fw_init - mlx5_load_one https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277211 Hopefully they would be fixed before March stabweek. We closed the stabilization period on Thursday. If you want to reap the fruits of the stabweek and you are very conservative and want to use only changes that passed certain level of testing, you can use the stabweek-2024-Feb branch. The branch is published at https://github.com/glebius/FreeBSD/tree/stabweek-2024-Feb. Otherwise I would recommend to use 7d233b2220cd3d23c028bdac7eb3b6b7b2025125 of FreeBSD/main as a good point to update. We did not observe any large or risky changes in main during the week. -- Gleb Smirnoff signature.asc Description: PGP signature
