From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, Zhenxian Ma <mzx199711@gmail.com>
Cc: hch@lst.de, bvanassche@acm.org,
syzbot+bd975ef54294bec73f0e@syzkaller.appspotmail.com,
Tal Zussman <tz2294@columbia.edu>,
Julian Sun <sunjunchao@bytedance.com>
Subject: Re: [PATCH v2] block: fix recursive i_rwsem locking in blkdev_write_iter()
Date: Tue, 27 Oct 2026 08:48:25 -0600 [thread overview]
Message-ID: <179311250504.921557.2007100010116005195.b4-ty@b4> (raw)
In-Reply-To: <20261022062513.77372-1-mzx199711@gmail.com>
On Thu, 22 Oct 2026 14:25:13 +0800, Zhenxian Ma wrote:
> Commit 2fec4fd97cc3 ("block: take i_rwsem for the direct I/O write
> fallback") takes i_rwsem around blkdev_buffered_write() in the direct
> write fallback to close a race with set_blocksize(). Commit
> 1b1be9ea4e34 ("block: take the inode lock for buffered write fallback")
> fixes the same race by taking i_rwsem inside blkdev_buffered_write()
> instead. With both commits applied, the fallback path takes i_rwsem
> recursively:
>
> [...]
Applied, thanks!
[1/1] block: fix recursive i_rwsem locking in blkdev_write_iter()
commit: 21b88cc8bafceee6c6c82503e3b2cc6f1d0c78bf
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2026-10-27 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 9:33 [PATCH] block: don't take i_rwsem twice in the direct write fallback Zhenxian Ma
2026-10-21 16:49 ` Bart Van Assche
2026-10-22 6:25 ` [PATCH v2] block: fix recursive i_rwsem locking in blkdev_write_iter() Zhenxian Ma
2026-10-22 16:19 ` Bart Van Assche
2026-10-27 6:14 ` Zhenxian Ma
2026-10-27 7:36 ` Shin'ichiro Kawasaki
2026-10-27 14:48 ` Jens Axboe [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=179311250504.921557.2007100010116005195.b4-ty@b4 \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=mzx199711@gmail.com \
--cc=sunjunchao@bytedance.com \
--cc=syzbot+bd975ef54294bec73f0e@syzkaller.appspotmail.com \
--cc=tz2294@columbia.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