From: Chandan Babu R <chandanbabu@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [BUG][xfstests generic/133] deadlock and crach on xfs, BUG: KASAN: slab-out-of-bounds in xfs_read_iomap_begin+0x5f2/0x750 [xfs]
Date: Thu, 08 Feb 2024 19:10:48 +0530 [thread overview]
Message-ID: <87r0hn3s0p.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20240208084616.6l3cfdelev7trv3w@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Thu, Feb 08, 2024 at 04:46:16 PM +0800, Zorro Lang wrote:
> Hi,
>
> Recently I hit a deadlock then panic at the end [1] by running
> xfstests generic/133 on x86_64 xfs with linux v6.8-rc3+. And
> it's reproducible by loop running g/133 many times.
>
> But I found that each time I hit this deadlock, the testing
> machine uses a *multi-stripes* disk/fs, likes:
>
> TEST_DEV:
> meta-data=/dev/sda2 isize=512 agcount=16, agsize=245744 blks
> = sectsz=512 attr=2, projid32bit=1
> = crc=1 finobt=1, sparse=1, rmapbt=0
> = reflink=1 bigtime=1 inobtcount=1 nrext64=1
> data = bsize=4096 blocks=3931904, imaxpct=25
> = sunit=16 swidth=32 blks
> naming =version 2 bsize=4096 ascii-ci=0, ftype=1
> log =internal log bsize=4096 blocks=16384, version=2
> = sectsz=512 sunit=16 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
> SCRATCH_DEV:
> meta-data=/dev/sda3 isize=512 agcount=16, agsize=245744 blks
> = sectsz=512 attr=2, projid32bit=1
> = crc=1 finobt=1, sparse=1, rmapbt=0
> = reflink=1 bigtime=1 inobtcount=1 nrext64=1
> data = bsize=4096 blocks=3931904, imaxpct=25
> = sunit=16 swidth=32 blks
> naming =version 2 bsize=4096 ascii-ci=0, ftype=1
> log =internal log bsize=4096 blocks=16384, version=2
> = sectsz=512 sunit=16 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
"Multiple stripes" is one of the configurations on which I execute
fstests. However, I noticed that my kernel build configuration did not have
KASAN enabled.
Even with KASAN enabled, I am unable to recreate the bug. I have executed
generic/133 test for 100 iterations on a kernel built from torvalds/master
branch.
How easy/difficult is it to recreate this bug on your test machine?
> I haven't reproduced this issue on a xfs with sunit=0 and swidth=0.
>
> The newest linux commit id (HEAD) which I used to hit this issue is
> (mainline linux):
>
> commit 547ab8fc4cb04a1a6b34377dd8fad34cd2c8a8e3
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Wed Feb 7 18:06:16 2024 +0000
>
> Merge tag 'loongarch-fixes-6.8-2' of git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson
>
--
Chandan
next prev parent reply other threads:[~2024-02-08 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 8:46 [BUG][xfstests generic/133] deadlock and crach on xfs, BUG: KASAN: slab-out-of-bounds in xfs_read_iomap_begin+0x5f2/0x750 [xfs] Zorro Lang
2024-02-08 13:40 ` Chandan Babu R [this message]
2024-02-09 4:22 ` Zorro Lang
2024-02-08 21:30 ` Dave Chinner
2024-02-20 5:49 ` Zorro Lang
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=87r0hn3s0p.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.