[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHk-=wgjTongV9B_2gSaY9xVhw9oK8Bc+uOara-CLuSsk7fBpQ@mail.gmail.com>
Date: Fri, 30 Apr 2021 12:02:19 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Rasmus Villemoes <linux@...musvillemoes.dk>,
Christoph Hellwig <hch@....de>,
"Darrick J. Wong" <djwong@...nel.org>, Jia He <justin.he@....com>,
Al Viro <viro@...iv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-xfs <linux-xfs@...r.kernel.org>,
Dave Chinner <david@...morbit.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Eric Sandeen <sandeen@...deen.net>,
Andy Shevchenko <andy.shevchenko@...il.com>
Subject: Re: [GIT PULL] iomap: new code for 5.13-rc1
On Fri, Apr 30, 2021 at 11:50 AM Eric W. Biederman
<ebiederm@...ssion.com> wrote:
>
> A printk specific variant could easily be modified to always restart or
> to simply ignore renames and changes to the mount tree.
Exactly. I think a "ignore renames and mount tree changes" version for
printk would be the right thing.
Yeah, you can in theory get inconsistent results, but everything is
RCU-protected, so you'd get the same kind of "its' kind of valid, but
in race situations you might get a mix of two components" that '%pd'
gives for a dentry case.
That would allow people to use '%pD' and get reasonable results,
without having them actually interact with locks (that may or may not
be held by the thread trying to print debug messages).
Linus
Powered by blists - more mailing lists