summaryrefslogtreecommitdiff
path: root/drivers/phy/axiado/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2026-07-31 10:36:05 +0200
committerChristian Brauner <brauner@kernel.org>2026-07-31 10:37:40 +0200
commitaa00a8fd9d4cbd863b9a85a464849b279a7674b1 (patch)
tree1875c672ebd6a40f08517fad122800bd2f607519 /drivers/phy/axiado/git@git.tavy.me:linux.git
parentb2f1e6301efa4a80becdb0715416c3cbc693fbb4 (diff)
fs/namei.c: update stale comments in lookup_open()
Commit ddb6e6c72a0a ("VFS: move mnt_want_write() and locking into lookup_open()") moved the parent inode locking into lookup_open(), but left the comment claiming the caller has to take it. A caller following that comment now deadlocks, and the series added a second caller. Describe what the function actually does. While at it drop the claim that it returns 0 on success and updates @path, wrong ever since lookup_open() started returning a dentry in v5.7, and fix the reference to lookup_open() in a comment that now sits inside lookup_open() itself. Link: https://patch.msgid.link/20260731-work-lookup-fixes-v1-1-2412b85cf65c@kernel.org Fixes: ddb6e6c72a0a ("VFS: move mnt_want_write() and locking into lookup_open()") Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'drivers/phy/axiado/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions