From: Matthew Wilcox <willy@infradead.org>
To: dm-devel@lists.linux.dev
Subject: next-20240412 warning in dm-bio-prison-v1.c
Date: Mon, 15 Apr 2024 17:22:39 +0100 [thread overview]
Message-ID: <Zh1UT__gACBnpfSd@casper.infradead.org> (raw)
Just got this splat running generic/347 with XFS on top.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1188676 at drivers/md/dm-bio-prison-v1.c:128 dm_cell_key_has_valid_range+0x3e/0x50
Modules linked in: crct10dif_generic crct10dif_common [last unloaded: crc_t10dif]
CPU: 0 PID: 1188676 Comm: kworker/u64:3 Not tainted 6.9.0-rc3-next-20240412-ktest-00036-g89ba24a9aade-dirty #13
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Workqueue: dm-thin do_worker
RIP: 0010:dm_cell_key_has_valid_range+0x3e/0x50
Code: e5 48 89 c1 48 29 d1 48 81 f9 00 04 00 00 77 1a 48 83 e8 01 48 c1 ea 0a b9 01 00 00 00 48 c1 e8 0a 48 39 c2 75 0c 89 c8 5d c3 <0f> 0b 31 c9 5d 89 c8 c3 0f 0b 31 c9 eb ee 0f 1f 40 00 f3 0f 1e fa
RSP: 0018:ffff888102453d28 EFLAGS: 00010206
RAX: 0000000000000fff RBX: 0000000000000000 RCX: 0000000000000fff
RDX: 0000000000000000 RSI: 0000000000000fff RDI: ffff888102453d40
RBP: ffff888102453d28 R08: ffff88810f897d00 R09: ff6d6867732c6c63
R10: 0000000000000018 R11: fefefefefefefeff R12: ffff88810f897c80
R13: ffff88813e0280b8 R14: 0000000000000fff R15: ffff88813e0280b8
FS: 0000000000000000(0000) GS:ffff888179600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9e1e6f27d0 CR3: 000000000202a000 CR4: 0000000000750eb0
PKRU: 55555554
Call Trace:
<TASK>
? show_regs+0x64/0x70
? __warn+0x88/0x120
? dm_cell_key_has_valid_range+0x3e/0x50
? report_bug+0x15d/0x180
? handle_bug+0x3e/0x70
? exc_invalid_op+0x1c/0x70
? asm_exc_invalid_op+0x1f/0x30
? dm_cell_key_has_valid_range+0x3e/0x50
process_discard_bio+0xa7/0x180
do_worker+0x81d/0xb90
process_one_work+0x135/0x2e0
worker_thread+0x2e8/0x420
? flush_delayed_work+0x50/0x50
kthread+0xd5/0x100
? kthread_park+0xa0/0xa0
ret_from_fork+0x3a/0x60
? kthread_park+0xa0/0xa0
ret_from_fork_asm+0x11/0x20
</TASK>
---[ end trace 0000000000000000 ]---
Hope that's useful.
reply other threads:[~2024-04-15 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Zh1UT__gACBnpfSd@casper.infradead.org \
--to=willy@infradead.org \
--cc=dm-devel@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).