From: Purva Yeshi <purvayeshi550@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Dave Kleikamp <shaggy@kernel.org>,
jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
syzbot+219127d0a3bce650e1b6@syzkaller.appspotmail.com
Subject: Re: [PATCH] fs: jfs: Avoid sleeping function call in softirq
Date: Tue, 25 Mar 2025 22:30:19 +0530 [thread overview]
Message-ID: <31800f57-2fd5-4e9b-a301-36a67ba27210@gmail.com> (raw)
In-Reply-To: <20250322143549.GH2023217@ZenIV>
On 22/03/25 20:05, Al Viro wrote:
> 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.
Thanks for the review. Based on your feedback, I have analyzed the call
path leading to fsync() being invoked in an invalid context. The issue
arises because generic_write_sync() is being called inside
dio_complete(), which can be triggered from dio_bio_end_aio().
dio_bio_end_aio() executes as a bio completion handler, which may run in
a SoftIRQ context. If dio_complete() is called directly (without
deferring), generic_write_sync() gets executed within SoftIRQ, which is
problematic since fsync() (invoked later) may sleep.
prev parent reply other threads:[~2025-03-25 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 14:21 Purva Yeshi
2025-03-22 14:35 ` Al Viro
2025-03-25 17:00 ` Purva Yeshi [this message]
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=31800f57-2fd5-4e9b-a301-36a67ba27210@gmail.com \
--to=purvayeshi550@gmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+219127d0a3bce650e1b6@syzkaller.appspotmail.com \
--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
all inboxes | Powered by JetHome®