All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Ian Kent <raven@themaw.net>
Cc: Brian Foster <bfoster@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] namei: clear nd->root.mnt before O_CREAT unlazy
Date: Fri, 7 Jan 2022 07:10:59 +0000	[thread overview]
Message-ID: <YdfngxyGWatLfa5h@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <YdfVG56XZnkePk7c@zeniv-ca.linux.org.uk>

On Fri, Jan 07, 2022 at 05:52:27AM +0000, Al Viro wrote:

> > Looks good, assuming Al is ok with the re-factoring.
> > Reviewed-by: Ian Kent <raven@themaw.net>
> 
> Ummm....  Mind resending that?  I'm still digging myself from under
> the huge pile of mail, and this seems to have been lost in process...

Non-obvious part is that current code only does this forgetting
the root when we are certain that we won't look at it later in
pathwalk.  IOW, it's guaranteed to be the same through the entire
thing.  This patch changes that; the final component may very well
be e.g. an absolute symlink.  We won't know that until we unlazy,
so we can't make forgetting conditional upon that.

I _think_ it's not going to lead to any problems, but I'll need to
take a good look at the entire thing after I get some sleep -
I'm about to fall down right now.

Other problems here (aside of whitespace damage - was that a
cut'n'paste of some kind?  Looks like 8859-1 NBSP for each
leading space...) are
	* misleading name of the new helper - it sounds like
"non-RCU side of complete_walk()" and that's not what it does
	* LOOKUP_CACHED needs to be mentioned in commit message
(it's incompatible with O_CREAT, so it couldn't occur on that
codepath - the transformation is an equivalent one, but that
ought to be mentioned)
	* the change I mentioned above needs to be in commit
message - this one is a lot more subtle.

Anyway, I'll look into that tomorrow - too sleepy right now
to do any serious analysis.

  parent reply	other threads:[~2022-01-07  7:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 18:02 [PATCH] namei: clear nd->root.mnt before O_CREAT unlazy Brian Foster
2022-01-06 23:46 ` Ian Kent
2022-01-07  5:52   ` Al Viro
2022-01-07  7:04     ` Ian Kent
2022-01-07  7:22       ` Al Viro
2022-01-07  7:10     ` Al Viro [this message]
2022-01-07 17:32       ` Brian Foster
2022-01-07 17:51         ` Al Viro
2022-01-07 18:42           ` Brian Foster
2022-01-08  3:26           ` Ian Kent

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=YdfngxyGWatLfa5h@zeniv-ca.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=bfoster@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=raven@themaw.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.