Any chance this can be landed in the next ~18 hours, aka before the weekly snapshot builds start at midnight UTC?

I was planning on sweeping the tree for MK_CAPSICUM and MK_CASPER soon. But I don't mind if you want to get started without me. ;-)

@andrew Any thoughts on Mark's comments?

LGTM.

Ping @salvadore ?

Fix typo

I didn't realize that the generate-release target existed when I was putting together the website bits for 13.3, but I'd like to use it for 14.1.

Fine with me. Installing updates from cron isn't particularly recommended, but there may be cases where it is appropriate.

In D44317#1011391, @jrtc27 wrote:

(The problem this fixes was introduced by me adding profiling to the linker in link_elf_ireloc.)

I'll note that amd64 initialises pcpu after link_elf_ireloc too, so things should really be consistent between the two, whether that's removing the added profiling or adding it to amd64 and hoisting the pcpu there. Otherwise it's harder to reason about where you can and can't use PCPU_*...

Isaac: Thanks for uploading this. The patch looks good aside from the extra line, but the commit message needs work to conform with FreeBSD norms -- we can work on that over email.

No objections from me, but I don't know enough about armv7 to know if produces working images.

Confirmed, this fixes the panic I'm seeing on EC2 arm64 instances.

I think it's worth leaving releng/1[12].* on the list precisely *because* secteam isn't supporting them... because there are still a nontrivial number of people running those releases (especially 12.4).