Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Feb 2024 23:33:22 +0100
From:      Alexander Leidinger <Alexander@Leidinger.net>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        Gleb Smirnoff <glebius@freebsd.org>, current@freebsd.org
Subject:   Re: February 2024 stabilization week
Message-ID:  <077f20a7155880c3b17c4dc571c8330e@Leidinger.net>
In-Reply-To: <ZdpPMSQRNXdmhmXc@kib.kiev.ua>
References:  <ZdlxzQJvbaDDIlnK@cell.glebi.us> <ZdpPMSQRNXdmhmXc@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)

--=_e9a42f543000acc2f35e73e0e3488d4b
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII;
 format=flowed

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 Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF

--=_e9a42f543000acc2f35e73e0e3488d4b
Content-Type: application/pgp-signature;
 name=signature.asc
Content-Disposition: attachment;
 filename=signature.asc;
 size=833
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmXabsEACgkQEg2wmwP4
2IbpAg/9H706lFY3jztQSxtw2AdWGW1Z6qpsvdi4wMg39dz0BFAa6pgSbIJ8QGAk
xnVDOzh+4pqEE50TqlHr/jWvvz6kAqaSeDxRoBOYx8GpLPNGdBxh4s4N3/WlQ12+
jV1/YaIav/XHOg+baRUNPzH4EB31h9CO6RxeYVSmu1IX3FMb8yGdWhJDeBBaNe9x
s8HUbSAkhjnZ5xBgf3P1Fc9oSrRlSOWif78wkh3lBHWbuwaPYArmr6B4QKPNbqby
Vucz/1qsvHIlzWTuUQ5CXrISpp6DTC76X/+KzEoNvGDnuRlsFkgD7eEvffTEOov8
Rx+XTZkeH19lH+vKo//gKQdhbwJ7QuC9j4P8xmXrd84GcGBbNtCJYbNmEJ2Vmz5G
JSIJwfyG2vn0FCpng0YnplLyIlx3jH9vQgbqG4qhBDIBn4wInDxy9SLa+ms4PyoM
0M/MokSJk+ge6HzO8bkvyGlCLXE63W3n4SAAsbGl8n/mXilz2GSBmglgw/p0syUQ
jCcoSOiIPyiIbleXjvBvJdTbTneV/qrF2GJI4VERw6sXrdwWBDhhBtjeC4wYbYkd
M34sjw7hvDlieVsj6bVeZBvEXJAIHjMxMR8uiDhrSC/9MFTSOMxixutxmTx4AIjW
XOt8YceI5sbjUCWhe+YsERgwn4FO0CzqlZQao5aHDk/5bM/+hyg=
=/6in
-----END PGP SIGNATURE-----

--=_e9a42f543000acc2f35e73e0e3488d4b--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?077f20a7155880c3b17c4dc571c8330e>