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
F131936263: D51233.id.diff
Sun, Oct 12, 8:21 AM
F131936259: D51233.id158257.diff
Sun, Oct 12, 8:21 AM
F131875946: D51233.diff
Sat, Oct 11, 9:40 PM
Unknown Object (File)
Thu, Oct 9, 8:58 PM
Unknown Object (File)
Tue, Oct 7, 10:17 AM
Unknown Object (File)
Fri, Oct 3, 6:54 AM
Unknown Object (File)
Wed, Oct 1, 5:58 AM
Unknown Object (File)
Fri, Sep 19, 12:39 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.