In-flight issues for FreeBSD 13.4-RELEASE
Issues being tracked leading up to FreeBSD 13.4-RELEASE. Please email re@ **as soon as you become aware of an issue**.
Issue identified
Issues start here.
* Further ICMP regressions in pf?
Issue assigned
A developer is responsible for making sure this is fixed in time for the release.
* loader-too-old warnings / loader updating instructions (imp)
Issue diagnosed
A developer is responsible for the issue and we think we know what is wrong.
Patch being tested
A developer has a possible fix.
Patched in HEAD
A patch has gone into HEAD.
Patched in STABLE
A patch has gone into the stable branch.
Merge approved
The release engineering team has approved merging the patch to the release branch.
Patched in release branch
A patch has gone into the release branch (or stable before the release branch is created).
Before BETA1:
* Boot problems with some Ryzen laptops (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270707) (jhb)
* Integer overflow in diff (https://reviews.freebsd.org/D46169) (des)
* Dhclient makes noise about SIP server option (https://reviews.freebsd.org/D45873) (michaelo)
* i386-on-amd64 cross-building differences (https://github.com/llvm/llvm-project/issues/99396) (dim, cperciva)
Before BETA2:
* sctp: improve input validation for data chunks (tuexen)
* ktrace: FreeBSD-SA-24:06.ktrace
* sshd: FreeBSD-SA-24:08.openssh
* cxgbe netmap flush frequency (markj)
* routing table issue with SLAAC (markj)
Before BETA3:
* vnet initialization fix (https://cgit.freebsd.org/src/commit/?id=9b569353e0b073a513cf10debbe634c2ceb29fdf) (tuexen)
* Typo in mailer.conf (marck)
* LLVM binaries sporadically build irreproducibly (dim)
* uio_iovcnt inconsistency (emaste)
* acl_copyin uninitialized memory (emaste)
* calendar setlogin issues (kevans)
* EFI loader binaries build irreproducibly (dim)
Before RC1:
* ICMP regression in FreeBSD-SA-24:05 (kp)
* tail -F crash (kib)
* adduser ZFS logic bugs (des)
Before RC2:
* add support for AMD Ryzen 7 "Phoenix" to amdtemp, amdsmn (delphij)
Won't fix
The issue won't be fixed in the release (it's too late and not critical enough to delay the release).