From: Chen Li <chenli@uniontech.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christian Brauner <christian.brauner@ubuntu.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ramfs: skip mknod if inode already exists.【请注意，邮件由batv+ae8989e1668f84a74d37+6506+infradead.org+hch@casper.srs.infradead.org代发】
Date: Wed, 16 Jun 2021 16:11:52 +0800 [thread overview]
Message-ID: <8735tigref.wl-chenli@uniontech.com> (raw)
In-Reply-To: <YMmHwTZaahtmjK2z@infradead.org>
On Wed, 16 Jun 2021 13:10:25 +0800,
Christoph Hellwig wrote:
>
> On Wed, Jun 16, 2021 at 10:53:12AM +0800, Chen Li wrote:
> >
> > It's possible we try to mknod a dentry, which have
> > already bound to an inode, just skip it.
>
> How do you think this could happen?
>
>
Sorry, that's my bad. I noticed unionfs used to do this check in 9c5b4452998c6e670cfde0928b277e9c50d9a676, but not sure is it a must.
next prev parent reply other threads:[~2021-06-16 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 2:53 [PATCH] ramfs: skip mknod if inode already exists Chen Li
2021-06-16 5:10 ` Christoph Hellwig
2021-06-16 8:11 ` Chen Li [this message]
2021-06-16 12:16 ` Al Viro
2021-06-17 1:13 ` [PATCH] ramfs: skip mknod if inode already exists.【请注意，邮件由viro@ftp.linux.org.uk代发】 Chen Li
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=8735tigref.wl-chenli@uniontech.com \
--to=chenli@uniontech.com \
--cc=akpm@linux-foundation.org \
--cc=christian.brauner@ubuntu.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).