From: Tejun Heo <tj@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: odd sysfs find behavior, was: Re: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification
Date: Wed, 21 Jun 2017 11:36:31 -0400 [thread overview]
Message-ID: <20170621153631.GA5267@htj.duckdns.org> (raw)
In-Reply-To: <20170621144826.GB15646@kroah.com>
Hello,
On Wed, Jun 21, 2017 at 10:48:26PM +0800, Greg Kroah-Hartman wrote:
> On Mon, Jun 19, 2017 at 01:59:34PM -0400, Tejun Heo wrote:
> > So, looks like this is the debugfs automount mechanism changing nlinks
> > across automounts and confusing find in the process. Greg?
>
> That's odd, is find racing with itself here? I don't really know how to
> do anything about this in sysfs, as this should happen for any other
> filesystem, right?
I don't actually know why find gets confused over nlinks changing
underneath it. Can't we also automount on the first stat(2) call?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-06-21 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170607094536.32419-1-jthumshirn@suse.de>
[not found] ` <20170615163141.GA27307@lst.de>
[not found] ` <bab953e9-7026-5833-9f65-1ef8b90433d7@suse.de>
[not found] ` <20170616094056.GA12465@lst.de>
[not found] ` <905ed2e6-1c1c-f3a3-5391-66e42fb61861@suse.de>
[not found] ` <20170616095837.GA14217@lst.de>
[not found] ` <CA+55aFxJ0bpRFsnZFe6sh2i4jxNdYmDi_6RZx2CQQdmQ_HU3wQ@mail.gmail.com>
2017-06-17 12:08 ` odd sysfs find behavior, was: Re: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification Christoph Hellwig
2017-06-18 1:12 ` Greg Kroah-Hartman
2017-06-18 7:32 ` Christoph Hellwig
[not found] ` <20170618073305.GB25797@lst.de>
2017-06-18 10:20 ` Tejun Heo
2017-06-18 10:32 ` Tejun Heo
2017-06-18 13:43 ` Christoph Hellwig
2017-06-19 17:59 ` Tejun Heo
2017-06-21 14:48 ` Greg Kroah-Hartman
2017-06-21 15:36 ` Tejun Heo [this message]
2017-06-22 0:21 ` Linus Torvalds
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=20170621153631.GA5267@htj.duckdns.org \
--to=tj@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).