Linux block layer
 help / color / mirror / Atom feed
From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Julian Sun <sunjunchao@bytedance.com>
Cc: linux-block@vger.kernel.org, jack@suse.cz, axboe@kernel.dk,
	 viro@zeniv.linux.org.uk, mcgrof@kernel.org, djwong@kernel.org,
	tz2294@columbia.edu
Subject: Re: [PATCH 2/2] block: take the inode lock for buffered write fallback
Date: Tue, 27 Oct 2026 16:29:16 +0900	[thread overview]
Message-ID: <auBSp6kmdP_E2JgJ@shinmob> (raw)
In-Reply-To: <b8e77932-d22d-4c08-b163-f60ffec25553@bytedance.com>

On Oct 27, 2026 / 14:13, Julian Sun wrote:
...
> > When I checking the new blktests test case block/050 by Tal Zussman [1], I found
> > the test case hangs [2]. I bisected and this kernel change triggers the hang.
> > 
> > Julian, may I ask you to take a look in the hang?
> 
> Hi Shin'ichiro,
> 
> Thanks for the report. This issue should be fixed by:
> https://lore.kernel.org/all/20261022062513.77372-1-mzx199711@gmail.com/
> 
> Could you please apply that patch and rerun block/050?

Thanks, the patch avoided the block/050 hang. Good.

  reply	other threads:[~2026-10-27  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  9:11 [PATCH 0/2] block: fix NOWAIT handling and locking in buffered write fallback Julian Sun
2026-10-15  9:11 ` [PATCH 1/2] block: reject NOWAIT " Julian Sun
2026-10-15  9:11 ` [PATCH 2/2] block: take the inode lock for " Julian Sun
2026-10-27  4:24   ` Shin'ichiro Kawasaki
2026-10-27  6:13     ` Julian Sun
2026-10-27  7:29       ` Shin'ichiro Kawasaki [this message]
2026-10-15 12:41 ` [PATCH 0/2] block: fix NOWAIT handling and locking in " Jens Axboe

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=auBSp6kmdP_E2JgJ@shinmob \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=sunjunchao@bytedance.com \
    --cc=tz2294@columbia.edu \
    --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