public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "hch@infradead.org" <hch@infradead.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	linux-block <linux-block@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	xfs <linux-xfs@vger.kernel.org>,
	Jack Vogel <jack.vogel@oracle.com>
Subject: Re: [RFC[RAP] 1/2] block: fix race between set_blocksize and read paths
Date: Fri, 18 Apr 2025 08:29:01 -0700	[thread overview]
Message-ID: <20250418152901.GI25659@frogsfrogsfrogs> (raw)
In-Reply-To: <xaqx4eiipvlytkx2vxxf3a25zxvn2vcj7kepcsjd34x6p3iy6w@fbvjbphgekb4>

On Fri, Apr 18, 2025 at 07:51:58AM +0000, Shinichiro Kawasaki wrote:
> On Apr 15, 2025 / 22:14, Christoph Hellwig wrote:
> > On Tue, Apr 15, 2025 at 10:01:44PM -0700, Darrick J. Wong wrote:
> > > It's the same patch as:
> > > https://lore.kernel.org/linux-fsdevel/20250408175125.GL6266@frogsfrogsfrogs/
> > > 
> > > which is to say, xfs/032 with while true; do blkid; done running in the
> > > background to increase the chances of a collision.
> > 
> > I think the xfs-zoned CI actually hit this with 032 without any extra
> > action the.
> 
> I observed xfs/032 hanged using the kernel on linux-xfs/for-next branch with git
> hash 71700ac47ad8. Before the hang, kernel reported the messages below:
> 
>   Oops: general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI
>   KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
>   CPU: 21 UID: 0 PID: 3187783 Comm: (udev-worker) Not tainted 6.15.0-rc1-kts-xfs-g71700ac47ad+ #1 PREEMPT(lazy)
>   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014
>   RIP: 0010:guard_bio_eod+0x52/0x5b0
> 
> The failure was recreated in stable manner. I applied this patch series, and
> confirmed the failure disappears. Good. (I needed to resolve conflicts, though)
> 
> This patch fixes block layer. So, IMO, it's the better to have a test case in
> blktests to confirm the fix. I created a blktests test case which recreates the
> failure using blockdev and fio commands. Will post it soon.

Ok.  I'll post a non-rfcrap version of the series shortly.  Thank you
for writing a regression test! :)

--D

      reply	other threads:[~2025-04-18 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15  0:14 [RFC[RAP] 1/2] block: fix race between set_blocksize and read paths Darrick J. Wong
2025-04-15  0:33 ` [RF[CRAP] 2/2] xfs: stop using set_blocksize Darrick J. Wong
2025-04-16  4:46   ` Christoph Hellwig
2025-04-16  5:06     ` Darrick J. Wong
2025-04-16  4:41 ` [RFC[RAP] 1/2] block: fix race between set_blocksize and read paths Christoph Hellwig
2025-04-16  5:01   ` Darrick J. Wong
2025-04-16  5:14     ` Christoph Hellwig
2025-04-18  7:51       ` Shinichiro Kawasaki
2025-04-18 15:29         ` Darrick J. Wong [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=20250418152901.GI25659@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=jack.vogel@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=willy@infradead.org \
    /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