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
F173052250: D12084.diff
Wed, Sep 23, 4:47 AM
Unknown Object (File)
Tue, Sep 22, 10:26 AM
Unknown Object (File)
Tue, Sep 22, 10:07 AM
Unknown Object (File)
Tue, Sep 22, 9:55 AM
Unknown Object (File)
Wed, Sep 9, 8:35 AM
Unknown Object (File)
Aug 16 2026, 8:24 AM
Unknown Object (File)
Aug 12 2026, 12:42 PM
Unknown Object (File)
Aug 12 2026, 12:17 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

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