Date: Mon, 25 Aug 2025 10:18:01 -0600 From: Warner Losh <imp@bsdimp.com> To: Kyle Evans <kevans@freebsd.org> Cc: Gleb Smirnoff <glebius@freebsd.org>, freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: August 2025 stabilization week Message-ID: <CANCZdfo7R8oT%2BNuBAM5C4HrRK4acAOmXrnRQWfJ2JB7o4nZLzA@mail.gmail.com> 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
[-- Attachment #1 --] On Mon, Aug 25, 2025 at 10:09 AM Kyle Evans <kevans@freebsd.org> wrote: > On 8/25/25 07:53, Gleb Smirnoff wrote: > > Hi, > > > > On Mon, Aug 25, 2025 at 01:00:07AM -0700, Gleb Smirnoff wrote: > > T> This is an automated email to inform you that the August 2025 > stabilization week > > T> started with FreeBSD/main at main-n279838-6c45a5dad0a0, which was > tagged as > > T> main-stabweek-2025-Aug. > > > > This stabilization cycle is expected to be more bumpy than usually. > > > > 1) We got major upgrade - OpenSSL 3.5.1. One known issue is that the > legacy > > provider is broken. > > > > 2) The default Kerberos now is MIT. We have already checked that a > Kerberized > > NFS client can migrate from Heimdal to MIT. We did not check Kerberized > NFS > > server, but should be fine. There is no yet an official way to migrate > kdc > > from Heimdal to MIT. So, if you are upgrading a machine that is kdc, > you need > > WITHOUT_MITKRB5="yes" in your src.conf. > > > > 3) The official pkg repo is now almost empty, see email from Colin [1]. > So, do > > not rush with 'make delete-old-libs', unless you are ready to build a > lot of > > packages yourself. > > > > 4) The unfortunate coincidence with 3) is ABI breakage in the > > setgroups(2)/getgroups(2) syscalls compared to the July stabilization > point. > > Some packages would dump core. These packages need to be rebuilt. > > > > This should be mitigated if you have COMPAT_FREEBSD14 enabled? Old > packages would > reference the old compat symbol versions in libc, which should use the > COMPAT_FREEBSD14 > variants of setgroups/getgroups. If you have a pointer to scenarios where > that isn't > the case, that'd be helpful- old packages should be fine in the GENERIC > case. > The packages that have been core dumping have so far all been SIGSYS not SIGSEGV which means Kyle's analysis is spot on. It's a fundamental use case that we powered through with even more radical changes like ino64. The only real problem one might encounter is if you install the new world, it uses the new system calls, but you have to revert the kernel to a one that only had the old version. Thankfully, regressions like this these days are are. I have another: 5) jemalloc was updated to 5.3.0, which in the past have had issues, but so far the only email has been a variation on thanking me for finally finding the time to get it in. Warner [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Aug 25, 2025 at 10:09 AM Kyle Evans <<a href="mailto:kevans@freebsd.org">kevans@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 8/25/25 07:53, Gleb Smirnoff wrote:<br> > Hi,<br> > <br> > On Mon, Aug 25, 2025 at 01:00:07AM -0700, Gleb Smirnoff wrote:<br> > T> This is an automated email to inform you that the August 2025 stabilization week<br> > T> started with FreeBSD/main at main-n279838-6c45a5dad0a0, which was tagged as<br> > T> main-stabweek-2025-Aug.<br> > <br> > This stabilization cycle is expected to be more bumpy than usually.<br> > <br> > 1) We got major upgrade - OpenSSL 3.5.1. One known issue is that the legacy<br> > provider is broken.<br> > <br> > 2) The default Kerberos now is MIT. We have already checked that a Kerberized<br> > NFS client can migrate from Heimdal to MIT. We did not check Kerberized NFS<br> > server, but should be fine. There is no yet an official way to migrate kdc<br> > from Heimdal to MIT. So, if you are upgrading a machine that is kdc, you need<br> > WITHOUT_MITKRB5="yes" in your src.conf.<br> > <br> > 3) The official pkg repo is now almost empty, see email from Colin [1]. So, do<br> > not rush with 'make delete-old-libs', unless you are ready to build a lot of<br> > packages yourself.<br> > <br> > 4) The unfortunate coincidence with 3) is ABI breakage in the<br> > setgroups(2)/getgroups(2) syscalls compared to the July stabilization point.<br> > Some packages would dump core. These packages need to be rebuilt.<br> > <br> <br> This should be mitigated if you have COMPAT_FREEBSD14 enabled? Old packages would<br> reference the old compat symbol versions in libc, which should use the COMPAT_FREEBSD14<br> variants of setgroups/getgroups. If you have a pointer to scenarios where that isn't<br> the case, that'd be helpful- old packages should be fine in the GENERIC case.<br></blockquote><div><br></div><div>The packages that have been core dumping have so far all been SIGSYS not SIGSEGV which means Kyle's analysis is spot on. It's a fundamental use case that we powered through with even more radical changes like ino64. The only real problem one might encounter is if you install the new world, it uses the new system calls, but you have to revert the kernel to a one that only had the old version. Thankfully, regressions like this these days are are.</div><div><br></div><div>I have another:</div><div><br></div><div>5) jemalloc was updated to 5.3.0, which in the past have had issues, but so far the only email has been a variation on thanking me for finally finding the time to get it in.</div><div><br></div><div>Warner</div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfo7R8oT%2BNuBAM5C4HrRK4acAOmXrnRQWfJ2JB7o4nZLzA>