From: Ingo Saitz <ingo@hannover.ccc.de>
To: linux-mm@kvack.org
Subject: Re: [linus:master] [mm] ba42b524a0: segfault_at_ip_sp_error
Date: Tue, 28 May 2024 22:52:41 +0200 [thread overview]
Message-ID: <ZlZEGUxdNIGfiBRu@spatz.zoo> (raw)
In-Reply-To: <202405281425.92ece916-lkp@intel.com>
I hit the same error on devuan unstable, with startpar crashing on boot:
[ 10.025881] dracut: Switching root
[ 10.339687] startpar[720]: segfault at 0 ip 0000000000000000 sp 00007fffbdca9c38 error 14 likely on CPU 1 (core 0, socket 0)
[ 10.340225] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 10.349516] startpar[820]: segfault at 0 ip 0000000000000000 sp 00007ffd52c34e48 error 14 likely on CPU 3 (core 1, socket 0)
[ 10.350086] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Setting init_mlocked_on_free=0 on the commandline mitigates this crash
and allows the system to boot successfully.
I managed to get a strace of startpar here:
https://hannover.ccc.de/~ingo/startpar-6.10-rc1/startpar.strace.txt.gz
Complete dmesg of the boot:
https://hannover.ccc.de/~ingo/startpar-6.10-rc1/dmesg-6.10-rc1.gz
I'm not sure if this actually is a kernel bug or if it is a classical
use after free that just got noticed by this change.
Ingo
--
const_cast<long double>(Λ)
next prev parent reply other threads:[~2024-05-28 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 7:00 [linus:master] [mm] ba42b524a0: segfault_at_ip_sp_error kernel test robot
2024-05-28 20:52 ` Ingo Saitz [this message]
2024-05-29 7:52 ` Ingo Saitz
2024-05-29 8:25 ` Ingo Saitz
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=ZlZEGUxdNIGfiBRu@spatz.zoo \
--to=ingo@hannover.ccc.de \
--cc=linux-mm@kvack.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.