[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgdr07iKGF2+9yPyW3SQN9qry_R0R45XYmdHHK1iFWNAQ@mail.gmail.com>
Date: Tue, 7 Feb 2023 11:09:31 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Eric Biggers <ebiggers@...nel.org>
Cc: Dan Carpenter <error27@...il.com>, linux-block@...r.kernel.org,
Julia Lawall <julia.lawall@...ia.fr>,
Luis Chamberlain <mcgrof@...nel.org>,
Hongchen Zhang <zhanghongchen@...ngson.cn>,
Alexander Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
"Christian Brauner (Microsoft)" <brauner@...nel.org>,
David Howells <dhowells@...hat.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
"Fabio M. De Francesco" <fmdefrancesco@...il.com>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
maobibo <maobibo@...ngson.cn>,
Matthew Wilcox <willy@...radead.org>,
Sedat Dilek <sedat.dilek@...il.com>
Subject: Re: block: sleeping in atomic warnings
On Tue, Feb 7, 2023 at 10:57 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> Looking at Jens' reply to the other cases, Dan's tool seems to be on
> the money here except for this self-inflicted bogus crypto key thing.
Oh, except you probably wouldn't have seen it, because Jens replied to
the original message where you weren't cc'd.
So here's the context for you wrt the other parts of the report:
https://lore.kernel.org/all/4321724d-9a24-926c-5d2d-5d5d902bda72@kernel.dk/
where there isn't that same indirection through the super-block, but
more of a clear-cut "this is all in the block layer".
Linus
Powered by blists - more mailing lists