[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZbkcaFYIv-FPj2Xj@infradead.org>
Date: Tue, 30 Jan 2024 07:57:28 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Jan Kara <jack@...e.cz>
Cc: syzbot <syzbot+69b40dc5fd40f32c199f@...kaller.appspotmail.com>,
akpm@...ux-foundation.org, axboe@...nel.dk, brauner@...nel.org,
chenzhongjin@...wei.com, dchinner@...hat.com, hch@...radead.org,
hch@....de, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, penguin-kernel@...ove.sakura.ne.jp,
syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk,
willy@...radead.org
Subject: Re: [syzbot] [fs?] BUG: sleeping function called from invalid
context in __getblk_gfp
On Tue, Jan 30, 2024 at 12:54:30PM +0100, Jan Kara wrote:
> sb_bread() under a RWLOCK - pointers_lock - in get_block(). Which more or
> less shows nobody has run sysv in ages because otherwise the chances of
> sleeping in atomic context are really high? Perhaps another candidate for
> removal?
I'd be fine with it, but I think Al has an attachment to it :)
Powered by blists - more mailing lists