Date: Fri, 27 Jun 2025 14:33:40 -0700 From: Gleb Smirnoff <glebius@freebsd.org> To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Closing: June 2025 stabilization week Message-ID: <aF8ONK2qb3VJBjqL@cell.glebi.us> In-Reply-To: <aFkJwZgyZXgZkXiX@cell.glebi.us>
index | next in thread | previous in thread | raw e-mail
On Mon, Jun 23, 2025 at 01:01:05AM -0700, Gleb Smirnoff wrote: T> This is an automated email to inform you that the June 2025 stabilization week T> started with FreeBSD/main at main-n278153-b2e0dfc808c1, which was tagged as T> main-stabweek-2025-Jun. This snapshot had 3 regressions identified, 2 of which are already addressed: 1) The disabled pathname expansion in rc(8) broke certain setups. The offending change had been reverted. Users of the stabweek snapshot are advised to cherry-pick: d783591a7deb and 9c014cc25c43 2) libtpool.so.2 was erroneously put into ObsoleteFiles.inc. A run of 'make delete-old-libs' or a fresh install of the stabweek snapshot ended in broken boot from a ZFS root. The problem was fixed by b5962a183756. This revision is also advised for cherry-pick. 3) Changes in OpenZFS induce performance degradation. See: https://github.com/openzfs/zfs/pull/17445#issuecomment-3009891003 This issue is still not resolved. Once resolved the StabWeeks wiki page will reflect that: https://wiki.freebsd.org/StabWeeks Note: in the Tuesday email I reported that at Netflix A/B testing we see increased wired memory use. This appeared to be a result of the conflict resolution mistake and does not apply to vanilla FreeBSD. -- Gleb Smirnoffhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aF8ONK2qb3VJBjqL>