From: David Sterba <dsterba@suse.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sam Sun <samsun1006219@gmail.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
syzkaller-bugs@googlegroups.com, xrivendell7@gmail.com,
reiserfs-devel@vger.kernel.org
Subject: Re: [Linux kernel bug] general protection fault in alloc_object
Date: Thu, 9 May 2024 17:45:20 +0200 [thread overview]
Message-ID: <20240509154520.GH13977@twin.jikos.cz> (raw)
In-Reply-To: <87pltwo056.ffs@tglx>
On Wed, May 08, 2024 at 04:20:53PM +0200, Thomas Gleixner wrote:
> On Tue, May 07 2024 at 14:32, Sam Sun wrote:
> > ```
> > general protection fault, probably for non-canonical address
> > 0xdffffc0040000001: 0000 [#1] PREEMPT SMP KASAN NOPTI
> > KASAN: probably user-memory-access in range
> > [0x0000000200000008-0x000000020000000f]
>
> This is a reiserfs issue. It crashes at random places:
>
> [ 348.634665][ T5992] REISERFS (device loop0): Using tea hash to sort names
> [ 348.780602][ T5993] (udev-worker)[5993]: segfault at 200000001 ip 0000000200000001 sp 00007fffca0e6190 error 14 in udevadm[5613a8f19000+1a000] likely on CPU 3 (core 0, socket 3)
> [ 348.796165][ T5993] Code: Unable to access opcode bytes at 0x1ffffffd7.
> [ 348.831600][ T5016] systemd-journald[5016]: /var/log/journal/a042c4e41bfd4c9697a628486ba7707d/system.journal: Journal file corrupted, rotating.
> [ 348.840565][ T6004] systemd-udevd[6004]: segfault at 100040048 ip 00007fde601b58a3 sp 00007fffca0e6250 error 4 in libc.so.6[7fde60108000+155000] likely on CPU 5 (core 0, socket 5)
> [ 348.844214][ T6004] Code: 89 10 49 8b b4 24 a8 10 00 00 eb 34 0f 1f 00 4c 8b 2d 69 f5 0f 00 64 45 8b 75 00 e8 27 42 fc ff e8 52 fe fa ff e9 01 fe ff ff <48> 8b 0a 48 8b 42 08 48 89 41 08 48 89 08 49 8b b4 24 a8 10 00 00
> [ 356.765557][ T5992] ==================================================================
> [ 356.767188][ T5992] BUG: unable to handle page fault for address: 0000000100040058
> [ 356.767204][ T5992] #PF: supervisor read access in kernel mode
> [ 356.767219][ T5992] #PF: error_code(0x0000) - not-present page
> [ 356.767233][ T5992] PGD 80000004ca01f067 P4D 80000004ca01f067 PUD 0
> [ 356.767266][ T5992] Oops: 0000 [#1] PREEMPT SMP KASAN PTI
> [ 356.767294][ T5992] CPU: 4 PID: 5992 Comm: a Not tainted 6.9.0-rc7-00012-gdccb07f2914c-dirty #43
> [ 356.767325][ T5992] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> [ 356.767342][ T5992] RIP: 0010:stack_depot_save_flags+0x14b/0x8e0
>
> Can we just get rid of this mess?
It's been on the deprecation and removal path, scheduled for 2025.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb103a51640ee32ab01c51e13bf8fca211f25f61
I wouldn't be surpised if somebody sends a patch on 1.1. to do that.
prev parent reply other threads:[~2024-05-09 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 6:32 [Linux kernel bug] general protection fault in alloc_object Sam Sun
2024-05-08 14:20 ` Thomas Gleixner
2024-05-09 15:45 ` David Sterba [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=20240509154520.GH13977@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=samsun1006219@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=xrivendell7@gmail.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.