vm_kern: in unback, init cursor while unlocked
ClosedPublic
Actions

Authored by dougm on Apr 15 2025, 3:56 AM.

Tags

None

Referenced Files

	Unknown Object (File)
	Tue, Dec 23, 9:26 AM

	Unknown Object (File)
	Thu, Dec 11, 12:09 PM

	Unknown Object (File)
	Thu, Dec 11, 5:27 AM

	Unknown Object (File)
	Fri, Nov 28, 12:29 PM

	Unknown Object (File)
	Nov 20 2025, 11:14 PM

	Unknown Object (File)
	Nov 10 2025, 11:29 PM

	Unknown Object (File)
	Nov 10 2025, 9:12 PM

	Unknown Object (File)
	Nov 10 2025, 7:42 PM

View All 60 Files

Subscribers

imp

Details

Reviewers

kib

Commits

rGadc33d3288e5: vm_kern: in unback, init cursor while unlocked

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

Closed by commit rGadc33d3288e5: vm_kern: in unback, init cursor while unlocked (authored by dougm). · Explain WhyApr 15 2025, 4:43 PM

This revision was automatically updated to reflect the committed changes.

dougm added a commit: rGadc33d3288e5: vm_kern: in unback, init cursor while unlocked.

Herald added a subscriber: imp. · View Herald TranscriptApr 15 2025, 4:43 PM