From: "'tj@kernel.org'" <tj@kernel.org>
To: "Hatayama, Daisuke" <d.hatayama@jp.fujitsu.com>
Cc: "'gregkh@linuxfoundation.org'" <gregkh@linuxfoundation.org>,
"Okajima, Toshiyuki" <toshi.okajima@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"'ebiederm@aristanetworks.com'" <ebiederm@aristanetworks.com>
Subject: Re: [RESEND PATCH v2] kernfs: fix dentry unexpected skip
Date: Fri, 1 Jun 2018 10:07:17 -0700 [thread overview]
Message-ID: <20180601170717.GY1351649@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <33710E6CAA200E4583255F4FB666C4E21B65779C@G01JPEXMBYT03>
Hello,
On Fri, Jun 01, 2018 at 09:25:32AM +0000, Hatayama, Daisuke wrote:
> kernfs_dir_pos() checks if a kernfs_node object given as one of its
> arguments is still active and if so returns it, or returns a
> kernfs_node object that is most equal (possibly smaller and larger) to
> the given object.
Sometimes they're duplicate operations tho, which is exactly the bug
the posted patch is trying to fix. What I'm suggesting is instead of
leaving both instances and skipping one conditionally, put them in one
place and trigger only when necessary. The sequence of operations
would be exactly the same. The only difference is how the code is
organized.
> kernfs_dir_next_pos() returns a kernfs_node object that is next to the
> object given by kernfs_dir_pos().
>
> Two functions does different things and both need to skip inactive
> nodes. I don't think it natural to remove the skip only from
> kernfs_dir_pos().
>
> OTOH, throughout getdents(), there is no case that the kernfs_node
> object given to kernfs_dir_pos() is used afterwards in the
> processing. So, is it enough to provide kernfs_dir_next_pos() only?
> Then, the skip code is now not duplicated.
>
> The patch below is my thought. How do you think?
>
> But note that this patch has some bug so that system boot get hang
> without detecting root filesystem disk :) I'm debugging this now.
I haven't looked into the code that closely but given that we had
cases where both skippings were fine and not, the condition is likely
gonna be a bit tricker?
Thanks.
--
tejun
next prev parent reply other threads:[~2018-06-01 17:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 12:54 [RESEND PATCH v2] kernfs: fix dentry unexpected skip Hatayama, Daisuke
2018-05-28 13:08 ` Hatayama, Daisuke
2018-05-29 16:26 ` 'tj@kernel.org'
2018-06-01 9:25 ` Hatayama, Daisuke
2018-06-01 17:07 ` 'tj@kernel.org' [this message]
2018-06-04 9:46 ` Hatayama, Daisuke
2018-06-02 17:25 ` Eric W. Biederman
2018-06-03 18:51 ` [CFT][PATCH] kernfs: Correct kernfs directory seeks Eric W. Biederman
2018-06-04 9:34 ` Hatayama, Daisuke
2018-06-04 14:44 ` Eric W. Biederman
2018-06-05 2:02 ` Eric W. Biederman
2018-06-05 5:52 ` Hatayama, Daisuke
2018-06-05 5:45 ` Hatayama, Daisuke
2018-06-05 15:31 ` Eric W. Biederman
2018-06-05 15:42 ` 'tj@kernel.org'
2018-06-05 17:47 ` Eric W. Biederman
2018-06-07 18:36 ` Al Viro
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=20180601170717.GY1351649@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=ebiederm@aristanetworks.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=toshi.okajima@jp.fujitsu.com \
/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