From: sashiko-bot@kernel.org
To: diasyzhangqing@gmail.com
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH v2] block: make bdev_freeze() mutex waits killable
Date: Wed, 11 Nov 2026 12:44:03 +0000 [thread overview]
Message-ID: <sashiko-outbox-209002@kernel.org> (raw)
In-Reply-To: <20261111123530.871952-1-diasyzhangqing@gmail.com>
> From: Qing Zhang <diasyzhang@tencent.com>
>
> Concurrent bdev_freeze() callers may wait a long time on
> bd_fsfreeze_mutex while another caller freezes and syncs the filesystem.
> Use mutex_lock_killable() to allow fatal signals to interrupt this wait.
>
> An interrupted wait returns -EINTR before bd_fsfreeze_count is
> incremented, so no freeze reference needs to be dropped. This does not
> make the filesystem freeze operation itself killable.
>
> Reported-by: syzbot+d4ecb9a1e5b3dcf8baec@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=d4ecb9a1e5b3dcf8baec
> Suggested-by: Jan Kara <jack@suse.cz>
> Signed-off-by: Qing Zhang <diasyzhang@tencent.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111123530.871952-1-diasyzhangqing@gmail.com?part=1
next prev parent reply other threads:[~2026-11-11 12:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 15:31 [syzbot] [block?] [ext4?] INFO: task hung in bdev_freeze syzbot
2026-11-10 13:21 ` [PATCH] ext4: make concurrent DEFAULT shutdown waits killable diasyzhangqing
2026-11-10 13:29 ` sashiko-bot
2026-11-10 13:35 ` Jan Kara
2026-11-11 3:27 ` diasyzhangqing
2026-11-11 3:38 ` sashiko-bot
2026-11-11 4:46 ` [syzbot] [block?] [ext4?] INFO: task hung in bdev_freeze syzbot
2026-11-10 21:34 ` syzbot
2026-11-11 12:35 ` [PATCH v2] block: make bdev_freeze() mutex waits killable diasyzhangqing
2026-11-11 12:44 ` sashiko-bot [this message]
2026-11-11 14:32 ` Jan Kara
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=sashiko-outbox-209002@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=diasyzhangqing@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tytso@mit.edu \
/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