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

On Fri, Jan 07, 2022 at 12:32:17PM -0500, Brian Foster wrote:

> > 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
> 
> Hmm.. I don't see any whitespace damage, even if I pull the patch back
> from the mailing list into my tree..?

That had occured in Ian's reply, almost certainly.  Looks like whatever
he's using for MUA (Evolution?) is misconfigured into doing whitespace
damage - his next mail (in utf8, rather than 8859-1) had a scattering of
U+00A0 in it...  Frankly, I'd never seen a decent GUI MUA, so I've no
real experience with that thing and no suggestions on how to fix that.

> > 	* misleading name of the new helper - it sounds like
> > "non-RCU side of complete_walk()" and that's not what it does
> 
> The intent was the opposite, of course. :P I'm not sure how you infer
> the above from _rcu(), but I'll name the helper whatever. Suggestions?

s/non-// in the above (I really had been half-asleep).  What I'm
saying is that this name invites an assumption that in RCU case
complete_walk() is equivalent to it.  Which is wrong - that's
what complete_walk() does as the first step if it needs to get
out of RCU mode.

  reply	other threads:[~2022-01-07 17:51 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
2022-01-07 17:32       ` Brian Foster
2022-01-07 17:51         ` Al Viro [this message]
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=Ydh9uKldc0cbusbt@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.