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] New: clone on sparc might fail with -EFAULT for no valid reason
Date: Fri, 16 Feb 2024 18:46:39 +0000 [thread overview]
Message-ID: <bug-31394-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31394
Bug ID: 31394
Summary: clone on sparc might fail with -EFAULT for no valid
reason
Product: glibc
Version: 2.38
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: sourceware-bugzilla at mkarcher dot dialup.fu-berlin.de
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Created attachment 15373
--> https://sourceware.org/bugzilla/attachment.cgi?id=15373&action=edit
issue reproducing program.
There seems to be a bug in the sparc and sparc64 linux kernel that results in
spurious -EFAULT errors from clone if %sp is referring to a stack address that
is not (yet) part of the program stack, as the stack is laziliy allocated.
I wrote a reproducer program to demonstrate the the presence of the issue, see
the attached file "more_clone_attack.c". As the reproducing script assumes the
stack bias of 0x7ff, it likely won't work as is on sparc32.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-02-16 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 18:46 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 18:52 ` 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@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).