public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sourceware-bugzilla at mkarcher dot dialup.fu-berlin.de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31394] clone on sparc might fail with -EFAULT for no valid reason Date: Fri, 16 Feb 2024 18:52:01 +0000 [thread overview] Message-ID: <bug-31394-131-ArNJpkyw9P@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31394-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31394 --- Comment #1 from Michael Karcher <sourceware-bugzilla at mkarcher dot dialup.fu-berlin.de> --- Created attachment 15374 --> https://sourceware.org/bugzilla/attachment.cgi?id=15374&action=edit patch to mitigate the kernel issue The issue has been obversed on a very wide range of kernel and glibc versions, e.g. on Debian wheezy (Linux 3.2.0 / glibc 2.13), but also on current gentoo machines (Linux 6.1 / glibc 2.38-r9). I developed a patch that causes the stack to be in a state that makes the system call clone work reliably, by first invoking flushw from userspace before entering the kernel. I believe the underlying issue is the way the kernel handles page faults during flushw ("The user stack is bolixed"), so I chose this way of pre-faulting the required pages. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-16 18:52 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-16 18:46 [Bug libc/31394] New: " sourceware-bugzilla at mkarcher dot dialup.fu-berlin.de 2024-02-16 18:52 ` sourceware-bugzilla at mkarcher dot dialup.fu-berlin.de [this message] 2024-02-16 18:52 ` [Bug libc/31394] " sourceware-bugzilla at mkarcher dot dialup.fu-berlin.de 2024-02-16 20:14 ` glaubitz at physik dot fu-berlin.de 2024-02-23 11:54 ` adhemerval.zanella at linaro dot org 2024-02-23 12:03 ` glaubitz at physik dot fu-berlin.de
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=bug-31394-131-ArNJpkyw9P@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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).