From: Dave Chinner <david@fromorbit.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
dm-devel@lists.linux.dev
Subject: [WARN 6.16-rc3] warning in bdev_count_inflight()
Date: Wed, 25 Jun 2025 18:26:14 +1000 [thread overview]
Message-ID: <aFuypjqCXo9-5_En@dread.disaster.area> (raw)
Hi Jens,
I had this warning fire on 6.16-rc3 whilst running fstests. I don't
know what test caused it - I run 64 tests in parallel over a couple
of hundred loop devices, so there's lots of stuff going on all the
time.
This warning fired when xfs_repair was running on some kind of DM
device:
[ 7339.374977] ------------[ cut here ]------------
[ 7339.378576] WARNING: CPU: 49 PID: 2034647 at block/genhd.c:144 bdev_count_inflight+0x7c/0x90
[ 7339.382933] Modules linked in:
[ 7339.385169] CPU: 49 UID: 0 PID: 2034647 Comm: xfs_repair Not tainted 6.16.0-rc3-dgc+ #342 PREEMPT(full)
[ 7339.390668] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 7339.396211] RIP: 0010:bdev_count_inflight+0x7c/0x90
[ 7339.399196] Code: ff 48 8b 94 16 90 00 00 00 01 d3 48 ff c0 eb bc 45 85 ff 78 15 85 db 78 1a 44 01 fb 89 d8 5b 41 5e 41 5f 5d c3 cc cc cc cc cc <0f> 0b 45 31 ff 85 db 79 e6 0f 0b 31 db eb e0 0f 1f 44 00 00 90 90
[ 7339.409039] RSP: 0018:ffffc900100bf978 EFLAGS: 00010286
[ 7339.412126] RAX: 0000000000000040 RBX: 0000000000000000 RCX: 0000000000000040
[ 7339.417910] RDX: 0000000000000040 RSI: 0000000000000040 RDI: ffffffff82f911c8
[ 7339.421923] RBP: ffffc900100bf990 R08: 0000000000000c00 R09: ffff889878c81400
[ 7339.425940] R10: 0000000000000000 R11: ffffffff823dc150 R12: 00000001006b668c
[ 7339.433641] R13: ffff889849c98600 R14: ffff889849c98600 R15: 00000000ffffffff
[ 7339.437308] FS: 00007f383ad55680(0000) GS:ffff88a09a4b1000(0000) knlGS:0000000000000000
[ 7339.441577] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7339.444716] CR2: 00007f3820000020 CR3: 0000001886ec6000 CR4: 0000000000350ef0
[ 7339.447851] Call Trace:
[ 7339.449436] <TASK>
[ 7339.450683] bdev_start_io_acct+0x58/0xc0
[ 7339.452661] dm_io_acct+0x60/0x100
[ 7339.454471] dm_submit_bio_remap+0x4f/0x100
[ 7339.456592] __map_bio+0x125/0x260
[ 7339.458423] dm_submit_bio+0x562/0xd70
[ 7339.459996] ? kmem_cache_alloc_noprof+0x188/0x320
[ 7339.462501] ? __blk_flush_plug+0xe6/0x140
[ 7339.464613] __submit_bio+0x12c/0x210
[ 7339.467010] submit_bio_noacct_nocheck+0x12e/0x2a0
[ 7339.469166] ? iov_iter_extract_pages+0x152/0x220
[ 7339.476238] submit_bio_noacct+0x2fd/0x380
[ 7339.478354] submit_bio+0xe5/0xf0
[ 7339.480182] submit_bio_wait+0x54/0xc0
[ 7339.481722] blkdev_direct_IO+0x415/0x480
[ 7339.483977] ? __pfx_submit_bio_wait_endio+0x10/0x10
[ 7339.487079] blkdev_read_iter+0x9d/0x170
[ 7339.494123] vfs_read+0x269/0x2f0
[ 7339.494131] __x64_sys_pread64+0x71/0xc0
[ 7339.494134] x64_sys_call+0x28ca/0x2f60
[ 7339.498789] do_syscall_64+0x6b/0x1f0
[ 7339.498794] ? exc_page_fault+0x70/0xa0
[ 7339.498798] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 7339.505840] RIP: 0033:0x7f383dd039ee
[ 7339.505845] Code: 08 0f 85 f5 4b ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 80 00 00 00 00 48 83 ec 08
[ 7339.505848] RSP: 002b:00007f383ad548e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000011
[ 7339.505851] RAX: ffffffffffffffda RBX: 00007f383ad55680 RCX: 00007f383dd039ee
[ 7339.505854] RDX: 0000000000000200 RSI: 000055f7bb191400 RDI: 0000000000000004
[ 7339.538888] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: {
[ 7339.541277] RBP: 0000000000000200 R08: 0000000000000000 R09: 0000000000000000
[ 7339.541282] R10: 000000001c200000 R11: 0000000000000246 R12: 00000000000e1000
[ 7339.544844] 49-....
[ 7339.548428] R13: 0000000000000001 R14: 00007f383ad54a60 R15: 000055f7bb186ae0
[ 7339.548433] </TASK>
I have no idea if it is reproducable - this is the first time I've
hit it. I've cc'd the DM list so they are aware of this, too.
-Dave.
--
Dave Chinner
david@fromorbit.com
next reply other threads:[~2025-06-25 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 8:26 Dave Chinner [this message]
2025-06-25 9:00 ` [WARN 6.16-rc3] warning in bdev_count_inflight() Dave Chinner
2025-06-25 14:48 ` Damien Le Moal
2025-06-25 14:49 ` Damien Le Moal
2025-06-25 11:28 ` Christoph Hellwig
2025-06-25 12:12 ` Dave Chinner
2025-06-25 12:13 ` Christoph Hellwig
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=aFuypjqCXo9-5_En@dread.disaster.area \
--to=david@fromorbit.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.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 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.