Page MenuHomeFreeBSD

inotify: do not call into namei() with a locked vnode
ClosedPublic

Authored by kib on Jul 10 2025, 7:17 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Nov 19, 10:51 PM
Unknown Object (File)
Fri, Nov 14, 11:50 AM
Unknown Object (File)
Thu, Nov 13, 10:48 PM
Unknown Object (File)
Thu, Nov 13, 8:41 PM
Unknown Object (File)
Fri, Nov 7, 1:15 AM
Unknown Object (File)
Wed, Oct 29, 12:17 PM
Unknown Object (File)
Wed, Oct 29, 11:52 AM
Unknown Object (File)
Oct 12 2025, 7:56 PM
Subscribers

Diff Detail

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

Event Timeline

kib requested review of this revision.Jul 10 2025, 7:17 AM

Thank you. I guess the problem arises when the directory is a mount point, and we need to upgrade the lock?

This revision is now accepted and ready to land.Jul 10 2025, 12:48 PM

Thank you. I guess the problem arises when the directory is a mount point, and we need to upgrade the lock?

For zfs, most likely it was a walk over the snapshot.
But it is generic rule that namei(9) must not be called while owning any vnode lock or busy reference on a mp. For instance, another reason might be non-shared locked fs, or non-recursive vnode lock.
As I noted in my mail to the list, the patch was a guess.