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
F114543328: D12084.id32256.diff
Sun, Apr 13, 8:35 PM
Unknown Object (File)
Wed, Apr 9, 1:07 PM
Unknown Object (File)
Wed, Apr 2, 3:30 AM
Unknown Object (File)
Fri, Mar 21, 12:36 AM
Unknown Object (File)
Mar 7 2025, 7:08 AM
Unknown Object (File)
Feb 8 2025, 1:00 PM
Unknown Object (File)
Jan 28 2025, 10:39 PM
Unknown Object (File)
Jan 13 2025, 11:48 PM
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

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 11172
Build 11553: arc lint + arc unit