From: Matthew Wilcox <willy@infradead.org>
To: Fengnan Chang <changfengnan@vivo.com>
Cc: miklos@szeredi.hu, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fuse: fix inconsistent status between faccess and mkdir
Date: Fri, 14 May 2021 03:26:30 +0100 [thread overview]
Message-ID: <YJ3f1lBkwY+9vqss@casper.infradead.org> (raw)
In-Reply-To: <20210514015517.258-1-changfengnan@vivo.com>
On Fri, May 14, 2021 at 09:55:17AM +0800, Fengnan Chang wrote:
> +++ b/fs/fuse/dir.c
> @@ -1065,6 +1065,14 @@ static int fuse_do_getattr(struct inode *inode, struct kstat *stat,
> fuse_fillattr(inode, &outarg.attr, stat);
> }
> }
> + if (err == -ENOENT) {
> + struct dentry *entry;
> +
> + entry = d_obtain_alias(inode);
Why d_obtain_alias() instead of d_find_any_alias()?
And what if you find the wrong alias? ie an inode with two links?
Or does fuse not support hardlinks?
next prev parent reply other threads:[~2021-05-14 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 1:55 [PATCH] fuse: fix inconsistent status between faccess and mkdir Fengnan Chang
2021-05-14 2:26 ` Matthew Wilcox [this message]
2021-05-14 3:27 ` 答复: " changfengnan
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=YJ3f1lBkwY+9vqss@casper.infradead.org \
--to=willy@infradead.org \
--cc=changfengnan@vivo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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;
as well as URLs for NNTP newsgroup(s).