[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250322143549.GH2023217@ZenIV>
Date: Sat, 22 Mar 2025 14:35:49 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Purva Yeshi <purvayeshi550@...il.com>
Cc: Dave Kleikamp <shaggy@...nel.org>, jfs-discussion@...ts.sourceforge.net,
linux-kernel@...r.kernel.org,
syzbot+219127d0a3bce650e1b6@...kaller.appspotmail.com
Subject: Re: [PATCH] fs: jfs: Avoid sleeping function call in softirq
On Sat, Mar 22, 2025 at 07:51:34PM +0530, Purva Yeshi wrote:
> Bug detected by Syzbot:
> BUG: sleeping function called from invalid context in jfs_fsync
>
> Fix jfs_fsync() to avoid sleeping in softirq/atomic, preventing crash.
> Skip execution in softirq/atomic and return -EWOULDBLOCK to prevent issues.
> Correct generic_file_fsync() call to pass the required arguments properly.
_ANY_ ->fsync() instance may sleep; adding that bandaid in jfs one does
not fix anything - the realy bug is whatever leads to having that
*called* in such conditions (e.g. having an unbalanced spin_lock()
somewhere, etc.)
NAK.
Powered by blists - more mailing lists