@vangyzen: are you interested in reviewing this? as you did the update jemalloc to 5.2.1.

Generally looks good to me.

Duplicate with D42436?

Sorry it takes me longer to review the code. Some suggestions:

In D42399#967703, @carlavilla wrote:

Ok, I’ll upgrade the news page and keep the others

I'm ok with 2012-compromise, or maybe ask secteam/clusteradm if they want to move to security/ or internal/.

In D42388#967250, @aokblast wrote:

The problem is found when I was looking at this issue.
Currently, -DWITH_ASAN cannot compile successfully before and after this patch.
After applying this patch, the error becomes:

ld: error: duplicate symbol: hexdump
>>> defined at sanitizer_common_interceptors.inc:10361 (/usr/src/contrib/llvm-project/compiler-rt/lib/sanitizer_common/sanitizer_common_interceptors.inc:10361)
>>>            asan_interceptors.o:(__interceptor_hexdump) in archive /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/clang/16/lib/freebsd/libclang_rt.asan-x86_64.a
>>> defined at mpsutil.c:166 (/usr/src/usr.sbin/mpsutil/mpsutil.c:166)
>>>            mpsutil.o:(.text+0x1350)

I think this is because userland has their own hexdump and also hexdump is a library call catched by asan.
I have no idea how to fix it. Maybe add blacklist on program defined their hexdump?
Hope anyone can give me some idea. Thanks!

We also need to remove OLD_FILES+=usr/share/man/man8/ping6.8.gz from ObsoleteFiles.inc.

In D42350#966388, @imp wrote:

Some tests don't run in jails. In addition to this cool feature it would be nice to be able to make tests as not for jail.

In D42271#964401, @salvadore wrote:

@lwhsu: On second thought, keep it as you proposed initially. It does not hurt to give an extra explanation in the body of the report and if we always used that footer, then it should be clear enough.

@salvadore if possible, I'd like to keep the explanation about the detail of the sponsorship. One reason is that we (at least me) don't want to let the donors of the foundation have an impression that we directly use their money to fix the specified issues in a company. The truth is that MS provides the engineer resources and hardware resource to support FreeBSD in their environment, and we just use their resource to publish our official images (and what we do is actually modify the release codes to match our requirements.)

Update the status of arm64 and mention mana work.

@mckusick thanks for the review and I will help to integrate this to the test suite.

I don't object removing the out of date contents, but may I suggest let's check if there is useful or historical contents and merge to the new place?