g: quoted-printable
Message-Id: <FBFB59E0-CFD3-46A6-A985-873FD1706655@yahoo.com>
References: <aO068RrAehdiHOoZ@www.zefox.net> <aRUJPryA4Vmu8dDD@www.zefox.net>
 <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org>
 <aRalt0YwsjV_mvMq@www.zefox.net> <87ldk9f4tt.wl-herbert@gojira.at>
 <CANCZdfrSaJ7snshhiV2r+EX_sazhJ-HFAK0e=q+-MOmP=uLKqg@mail.gmail.com>
 <aRnxOtZ8W2g6ZkVF@www.zefox.net>
 <CANCZdfqTZ311DGEQmH0FLKrh8csN-P=qwUt=RXGSTrehUfZi3g@mail.gmail.com>
 <aR_dxBLhRtcBq5k1@www.zefox.net>
 <40BEA46A-96CE-46A1-A994-B8470EE0C844@yahoo.com>
 <aSB9bPbs9QsDb1vR@www.zefox.net>
To: bob prohaska <fbsd@www.zefox.net>
X-Mailer: Apple Mail (2.3826.700.81)
X-Spamd-Bar: ---
X-Spamd-Result: default: False [-4.00 / 15.00];
	NEURAL_HAM_MEDIUM(-1.00)[-1.000];
	NEURAL_HAM_LONG(-1.00)[-1.000];
	NEURAL_HAM_SHORT(-1.00)[-0.997];
	DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject];
	R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048];
	R_SPF_ALLOW(-0.20)[+ptr:yahoo.com];
	MIME_GOOD(-0.10)[text/plain];
	FROM_HAS_DN(0.00)[];
	RCVD_TLS_LAST(0.00)[];
	RCPT_COUNT_TWO(0.00)[2];
	TO_DN_EQ_ADDR_SOME(0.00)[];
	MIME_TRACE(0.00)[0:+];
	DWL_DNSWL_NONE(0.00)[yahoo.com:dkim];
	ARC_NA(0.00)[];
	FREEMAIL_FROM(0.00)[yahoo.com];
	TO_DN_SOME(0.00)[];
	DKIM_TRACE(0.00)[yahoo.com:+];
	ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US];
	RCVD_VIA_SMTP_AUTH(0.00)[];
	TO_MATCH_ENVRCPT_SOME(0.00)[];
	RCVD_COUNT_TWO(0.00)[2];
	FROM_EQ_ENVFROM(0.00)[];
	FREEMAIL_ENVFROM(0.00)[yahoo.com];
	MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org];
	BLOCKLISTDE_FAIL(0.00)[98.137.64.146:server fail];
	MID_RHS_MATCH_FROM(0.00)[];
	APPLE_MAILER_COMMON(0.00)[];
	RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.146:from];
	RCVD_IN_DNSWL_NONE(0.00)[98.137.64.146:from]
X-Rspamd-Queue-Id: 4dQSrM2dDrz46wy

There was a commit on "Mon, 08 Dec 2025":

    =E2=80=A2 git: cff67bc43df1 - main - vm_fault: only rely on PG_ZERO =
when the page was newly allocated Konstantin Belousov

This looks to be more changes related to avoiding the "p[i] =3D=3D 0"
problem taht jemalloc was detecting and reporting:

QUOTE
    vm_fault: only rely on PG_ZERO when the page was newly allocated

If the fs->m page was found invalid on the object queue, PG_ZERO flag is
stale. Track the source of the page in the new fault state variable
m_needs_zero, and ignore PG_ZERO if the page did not came from the
allocator.
END QUOTE

It is indicated for a MFC in 1 week.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com