nullfs: reduce areas protected by vnode interlock in null_lock
ClosedPublic
Actions

Authored by mjg on Aug 31 2019, 9:58 AM.

Tags

None

Referenced Files

	F140127561: D21480.id61503.diff
	Sat, Dec 20, 2:53 PM

	F140085358: D21480.diff
	Sat, Dec 20, 1:10 AM

	Unknown Object (File)
	Fri, Nov 28, 3:35 PM

	Unknown Object (File)
	Fri, Nov 28, 11:23 AM

	Unknown Object (File)
	Mon, Nov 24, 12:10 PM

	Unknown Object (File)
	Sun, Nov 23, 6:14 PM

	Unknown Object (File)
	Thu, Nov 20, 8:27 PM

	Unknown Object (File)
	Thu, Nov 20, 8:14 PM

View All Files

Subscribers

imp

Details

Reviewers

kib

Commits

rS351651: nullfs: reduce areas protected by vnode interlock in null_lock

Summary

Similarly to the other routine stop taking the interlock for the lower vnode. The interlock for nullfs vnode is still taken to ensure stability of ->v_data.

Diff Detail

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

mjg created this revision.Aug 31 2019, 9:58 AM

Herald added a subscriber: imp. · View Herald TranscriptAug 31 2019, 9:58 AM

Harbormaster completed remote builds in B26207: Diff 61502.Aug 31 2019, 9:58 AM

wrong diff

clear the interlock flag for the fallback case

kib accepted this revision.Aug 31 2019, 3:17 PM

This revision is now accepted and ready to land.Aug 31 2019, 3:17 PM

Closed by commit rS351651: nullfs: reduce areas protected by vnode interlock in null_lock (authored by mjg). · Explain WhySep 1 2019, 2:52 AM

This revision was automatically updated to reflect the committed changes.

mjg added a commit: rS351651: nullfs: reduce areas protected by vnode interlock in null_lock.

Revision Contents
Changeset List

Path

Size

sys/

fs/

nullfs/

null_vnops.c

13 lines

Diff 61503

View Options

sys/fs/nullfs/null_vnops.c

nullfs: reduce areas protected by vnode interlock in null_lockClosedPublicActions