From: "Uwe Kleine-König" <ukleinek@debian.org>
To: Alexis Huxley <alexishuxley@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
1101944@bugs.debian.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: Bug#1101944: list_del corruption ... kernel BUG at lib/list_debug.c:62!
Date: Wed, 30 Apr 2025 21:17:36 +0200 [thread overview]
Message-ID: <pasokojf3peylxcuearrrqjfbpgqm3k37kpxnm7sxfpgxfm5b5@puxeitmfbzoa> (raw)
In-Reply-To: <aAjayRnB3bi1T_tk@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2716 bytes --]
Hello Alexis,
On Wed, Apr 23, 2025 at 01:19:21PM +0100, Matthew Wilcox wrote:
> On Wed, Apr 23, 2025 at 10:52:27AM +0200, Uwe Kleine-König wrote:
>
> [trimmed all the irrelevant garbage from the start of each line]
As Matthew pointed out the output of the CHECK_DATA_CORRUPTION would be
interesting. Can you please check if you can find this line still in
your journal?
> > ------------[ cut here ]------------
> > kernel BUG at lib/list_debug.c:62!
>
> That's:
>
> CHECK_DATA_CORRUPTION(next->prev != entry,
> "list_del corruption. next->prev should be %px, but was %px. (next=%px)\n",
> entry, next->prev, next))
> return false;
>
> Unfortunately, I don't see that rather useful information in this
> report.
>
> > invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
> > CPU: 10 PID: 6770 Comm: python3 Not tainted 6.1.0-32-amd64 #1 Debian 6.1.129-1
> > Hardware name: Gigabyte Technology Co., Ltd. Z790 AERO G/Z790 AERO G, BIOS F13b 12/04/2024
> > RIP: 0010:__list_del_entry_valid.cold+0x23/0x6f
> > Code: e8 0d 9f fe ff 0f 0b 48 89 fe 48 c7 c7 98 62 fa bc e8 fc 9e fe ff 0f 0b 48 89 d1 48 c7 c7 b8 63 fa bc 48 89 c2 e8 e8 9e fe ff <0f> 0b 48 89 f2 48 89 fe 48 c7 c7 68 63 fa bc e8 d4 9e fe ff 0f 0b
> > RSP: 0000:ffffa9fba3247b60 EFLAGS: 00010046
> > RAX: 000000000000006d RBX: ffff9ba2bf6b78e8 RCX: 0000000000000000
> > RDX: 0000000000000000 RSI: ffff9ba2bf6a03a0 RDI: ffff9ba2bf6a03a0
> > RBP: 0000000000000010 R08: 0000000000000000 R09: ffffa9fba32479f8
> > R10: 0000000000000003 R11: ffff9ba2ffb75fe8 R12: 0000000000000000
> > R13: ffffd11bca09ac88 R14: ffff9ba2ffbd5c00 R15: 0000000000000000
> > FS: 00007f9245392740(0000) GS:ffff9ba2bf680000(0000) knlGS:0000000000000000
> > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > CR2: 00007f92449af024 CR3: 000000074b884000 CR4: 0000000000752ee0
> > PKRU: 55555554
> > Call Trace:
> > <TASK>
> > ? __die_body.cold+0x1a/0x1f
> > ? die+0x2a/0x50
> > ? do_trap+0xc5/0x110
> > ? __list_del_entry_valid.cold+0x23/0x6f
> > ? do_error_trap+0x6a/0x90
> > ? __list_del_entry_valid.cold+0x23/0x6f
> > ? exc_invalid_op+0x4c/0x60
> > ? __list_del_entry_valid.cold+0x23/0x6f
> > ? asm_exc_invalid_op+0x16/0x20
> > ? __list_del_entry_valid.cold+0x23/0x6f
> > rmqueue_bulk+0x124/0x5d0
> > get_page_from_freelist+0xbae/0x11b0
>
> We're in the page allocator. There's nothing particularly exciting to
> be found in this backtrace, but in future, running it through
> scripts/decode_stacktrace.sh can be very helpful.
I can do that. Will follow up when I find the time.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-30 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 8:52 Uwe Kleine-König
2025-04-23 12:19 ` Matthew Wilcox
2025-04-30 19:17 ` Uwe Kleine-König [this message]
2025-05-01 12:52 ` Bug#1101944: " Alexis Huxley
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=pasokojf3peylxcuearrrqjfbpgqm3k37kpxnm7sxfpgxfm5b5@puxeitmfbzoa \
--to=ukleinek@debian.org \
--cc=1101944@bugs.debian.org \
--cc=akpm@linux-foundation.org \
--cc=alexishuxley@gmail.com \
--cc=linux-mm@kvack.org \
--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