Page MenuHomeFreeBSD

vm_kern: in unback, init cursor while unlocked
ClosedPublic

Authored by dougm on Apr 15 2025, 3:56 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 20, 11:14 PM
Unknown Object (File)
Mon, Nov 10, 11:29 PM
Unknown Object (File)
Mon, Nov 10, 9:12 PM
Unknown Object (File)
Mon, Nov 10, 7:42 PM
Unknown Object (File)
Mon, Nov 10, 6:57 PM
Unknown Object (File)
Sat, Nov 8, 4:43 AM
Unknown Object (File)
Wed, Nov 5, 10:56 AM
Unknown Object (File)
Wed, Nov 5, 10:55 AM
Subscribers

Details

Summary

In kmem_unback(), take one small bit of code out of the region where the write lock is held.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

dougm requested review of this revision.Apr 15 2025, 3:56 AM
dougm created this revision.

Something (un)related: Can we somehow automate checking for the issue where iterators are invalidated due to the object unlock? For instance, we can add the object' lock generation for INVARIANTS kernels, remember the current generation in the iterator on init, and assert that the lock generation does not change on next access to the iterator.

This revision is now accepted and ready to land.Apr 15 2025, 10:46 AM
This revision was automatically updated to reflect the committed changes.