To: bob prohaska <fbsd@www.zefox.net> 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%2BEX_sazhJ-HFAK0e=q%2B-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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FBFB59E0-CFD3-46A6-A985-873FD1706655>