Page MenuHomeFreeBSD

Synchronize page laundering with pmap_extract_and_hold()
ClosedPublic

Authored by markj on Aug 19 2017, 9:33 PM.
Tags
None
Referenced Files
F145013696: D12084.id.diff
Sun, Feb 15, 1:32 AM
Unknown Object (File)
Thu, Feb 12, 2:54 PM
Unknown Object (File)
Sat, Jan 31, 12:13 PM
Unknown Object (File)
Jan 13 2026, 11:32 PM
Unknown Object (File)
Nov 25 2025, 3:26 PM
Unknown Object (File)
Nov 21 2025, 3:00 AM
Unknown Object (File)
Nov 21 2025, 2:59 AM
Unknown Object (File)
Nov 21 2025, 2:57 AM
Subscribers
None

Details

Summary

The hold_count check in vm_pageout_cluster() is susceptible to a race
with pmap_extract_and_hold() since the latter may be called without the
object lock or vnode lock held. In particular, there is a window between
the hold_count check and the later pmap_remove_write() call during which
a concurrent pmap_extract_and_hold() caller may obtain write access to
pages in the cluster. This appears to be a regression from r207410.

Attempt to handle this by atomically checking hold_count and removing
managed write mappings when adding a page to a pageout cluster. Note
that vm_object_page_collect_flush() ensures that the clustered pages
are read-only.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable