Date: Mon, 25 Aug 2025 11:53:14 -0700 From: Gleb Smirnoff <glebius@freebsd.org> To: Kyle Evans <kevans@freebsd.org> Cc: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: August 2025 stabilization week Message-ID: <aKyxGl3WsZtHuAbt@cell.glebi.us> In-Reply-To: <56dd78c6-a53a-4c4c-989a-335cc5fed405@FreeBSD.org> References: <aKwYB4d6l4ze-yXA@cell.glebi.us> <aKxcwqKqW3ZpA3Po@cell.glebi.us> <56dd78c6-a53a-4c4c-989a-335cc5fed405@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Mon, Aug 25, 2025 at 11:09:36AM -0500, Kyle Evans wrote: K> > 4) The unfortunate coincidence with 3) is ABI breakage in the K> > setgroups(2)/getgroups(2) syscalls compared to the July stabilization point. K> > Some packages would dump core. These packages need to be rebuilt. K> K> This should be mitigated if you have COMPAT_FREEBSD14 enabled? Old packages would K> reference the old compat symbol versions in libc, which should use the COMPAT_FREEBSD14 K> variants of setgroups/getgroups. If you have a pointer to scenarios where that isn't K> the case, that'd be helpful- old packages should be fine in the GENERIC case. You are correct. This affects only people who run custom kernels without COMPAT_FREEBSD14. -- Gleb Smirnoffhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aKyxGl3WsZtHuAbt>