From: Ingo Saitz <ingo@hannover.ccc.de>
To: linux-mm@kvack.org
Subject: Re: [linus:master] [mm] ba42b524a0: segfault_at_ip_sp_error
Date: Wed, 29 May 2024 09:52:44 +0200 [thread overview]
Message-ID: <ZlbezNiM-8kge7lo@spatz.zoo> (raw)
In-Reply-To: <ZlZEGUxdNIGfiBRu@spatz.zoo>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Tue, May 28, 2024 at 10:52:41PM +0200, Ingo Saitz wrote:
> 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.
I can reproduce the error with the attached c program.
[ 1325.980596] thoughts[2127]: segfault at 0 ip 0000000000000000 sp 00007fff183d66e8 error 14 likely on CPU 0 (core 0, socket 0)
[ 1325.981180] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Simply calling mlockall(MCL_CURRENT) and then fork() seems to be enough
to trigger the error.
Ingo
--
const_cast<long double>(Λ)
[-- Attachment #2: thoughts.c --]
[-- Type: text/x-csrc, Size: 428 bytes --]
#define _GNU_SOURCE
#include <signal.h>
#include <stdio.h>
#include <stdlib.h>
#include <sys/mman.h>
#include <sys/select.h>
#include <unistd.h>
int main() {
mlockall(MCL_CURRENT);
pid_t pid = fork();
if (pid == 0) {
_exit(0);
}
const struct timespec zero = {2, 0};
sigset_t smask;
sigemptyset(&smask);
pselect(0, 0, 0, 0, &zero, &smask);
printf("Success on pid %d\n", pid);
}
next prev parent reply other threads:[~2024-05-29 7: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
2024-05-29 7:52 ` Ingo Saitz [this message]
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=ZlbezNiM-8kge7lo@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.