From: hooanon05g@gmail.com
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: v7.0-rc1, name_to_handle_at(..., AT_EMPTY_PATH)
Date: Sat, 28 Feb 2026 07:35:25 +0900 [thread overview]
Message-ID: <13485.1772231725@jrotkm2> (raw)
In-Reply-To: <20260227184804.GC3836593@ZenIV>
Al Viro:
> The last point where LOOKUP_EMPTY (or AT_EMPTY_PATH) matters is (and had
> always been) getname_flags(); pathname resolution proper doesn't care.
Filesystems recieved LOOKUP_EMPTY before v7.0-rc1 and could use it to
detect a case like this.
fd = open("fileA");
unlink("fileA");
name_to_handle_at(fd, "", fh, &mnt_id, AT_EMPTY_PATH);
The flag was used to support
- unlinked but still alive inode
- without its name
and d_revalidate() should handle it still valid.
Yes, the filesystem is out-of-tree.
Now I understand that LOOKUP_EMPTY is not passed to filesystem
intentionally.
Thank you
J. R. Okajima
prev parent reply other threads:[~2026-02-27 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 10:44 v7.0-rc1, name_to_handle_at(..., AT_EMPTY_PATH) J. R. Okajima
2026-02-27 15:22 ` Al Viro
2026-02-27 15:41 ` hooanon05g
2026-02-27 18:48 ` Al Viro
2026-02-27 20:07 ` Al Viro
2026-02-27 22:35 ` hooanon05g [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13485.1772231725@jrotkm2 \
--to=hooanon05g@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox