From: Linus Torvalds <torvalds@linux-foundation.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>, Jia He <justin.he@arm.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [GIT PULL] iomap: new code for 5.13-rc1
Date: Wed, 28 Apr 2021 09:50:01 -0700 [thread overview]
Message-ID: <CAHk-=wimsMqGdzik187YWLb-ru+iktb4MYbMQG1rnZ81dXYFVg@mail.gmail.com> (raw)
In-Reply-To: <1de23de2-12a9-2b13-3b86-9fe4102fdc0c@rasmusvillemoes.dk>
[ Added Andy, who replied to the separate thread where Jia already
posted the patch ]
On Wed, Apr 28, 2021 at 12:38 AM Rasmus Villemoes
<linux@rasmusvillemoes.dk> wrote:
>
> So the patch makes sense to me. If somebody says '%pD5', it would get
> capped at 4 instead of being forced down to 1. But note that while that
> grep only produces ~36 hits, it also affects %pd, of which there are
> ~200 without a 2-4 following (including some vsprintf test cases that
> would break). So I think one would first have to explicitly support '1',
> switch over some users by adding that 1 in their format string
> (test_vsprintf in particular), then flip the default for 'no digit
> following %p[dD]'.
Yeah, and the "show one name" actually makes sense for "%pd", because
that's about the *dentry*.
A dentry has a parent, yes, but at the same time, a dentry really does
inherently have "one name" (and given just the dentry pointers, you
can't show mount-related parenthood, so in many ways the "show just
one name" makes sense for "%pd" in ways it doesn't necessarily for
"%pD"). But while a dentry arguably has that "one primary component",
a _file_ is certainly not exclusively about that last component.
So you're right - my "how about something like this" patch is too
simplistic. The default number of components to show should be about
whether it's %pd or %pD.
That also does explain the arguably odd %pD defaults: %pd came first,
and then %pD came afterwards.
Linus
next prev parent reply other threads:[~2021-04-28 16:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 2:58 [GIT PULL] iomap: new code for 5.13-rc1 Darrick J. Wong
2021-04-27 19:40 ` Linus Torvalds
2021-04-27 19:57 ` Christoph Hellwig
2021-04-27 20:05 ` Linus Torvalds
2021-04-28 6:17 ` Christoph Hellwig
2021-04-28 6:38 ` Linus Torvalds
2021-04-28 6:41 ` Christoph Hellwig
2021-04-28 7:14 ` Linus Torvalds
2021-04-28 7:38 ` Rasmus Villemoes
2021-04-28 8:47 ` Justin He
2021-04-28 16:50 ` Linus Torvalds [this message]
2021-04-29 6:39 ` Rasmus Villemoes
2021-04-29 16:45 ` Linus Torvalds
2021-04-30 3:17 ` Justin He
2021-04-30 3:21 ` Al Viro
2021-04-30 6:13 ` Justin He
2021-04-30 18:58 ` Linus Torvalds
2021-04-30 18:50 ` Eric W. Biederman
2021-04-30 19:02 ` Linus Torvalds
2021-04-29 6:43 ` Christoph Hellwig
2021-04-27 20:07 ` pr-tracker-bot
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='CAHk-=wimsMqGdzik187YWLb-ru+iktb4MYbMQG1rnZ81dXYFVg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=justin.he@arm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=sandeen@sandeen.net \
--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).