Date: Sat, 28 Sep 2024 23:10:57 +0100 From: void <void@f-m.fm> To: freebsd-current@freebsd.org Cc: src-committers@freebsd.org Subject: Re: September 2024 stabilization week Message-ID: <Zvh-8cMF_HtOJ3uu@int21h> In-Reply-To: <ZvRze1gldJTCvjir@cell.glebi.us> References: <ZvEgC9ak7paxygYw@cell.glebi.us> <ZvRze1gldJTCvjir@cell.glebi.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Gleb, On Wed, Sep 25, 2024 at 01:32:59PM -0700, Gleb Smirnoff wrote: >On Mon, Sep 23, 2024 at 01:00:11AM -0700, Gleb Smirnoff wrote: >T> This is an automated email to inform you that the September 2024 stabilization week >T> started with FreeBSD/main at main-n272449-6e414739fc95, which was tagged as >T> main-stabweek-2024-Sep. > >The only issue discovered at Netflix testing is regression with ixl(4) >14561f1eda85 that has already been reverted with bf085659dac9. If you run with >the main-stabweek-2024-Sep and use ixl(4) NIC you need to cherry-pick >bf085659dac9. Other than that, no problems found. I have found that *only* on arm64, locate errors like so: # sh /etc/periodic/weekly/310.locate Rebuilding locate database: install: /var/db/INS@ArwCNx: Permission denied However, if it's run like this: # sh /usr/libexec/locate.updatedb >>> WARNING >>> Executing updatedb as root. This WILL reveal all filenames >>> on your machine to all login users, which is a security risk. it exits normally. Moving /var/db/locate.database aside makes no difference. The problem doesn't happen on amd64 arch, same 6e414739fc95. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zvh-8cMF_HtOJ3uu>