public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31402] New: clone (NULL, NULL, ...) clobbers %r7 register on s390{,x} Date: Mon, 19 Feb 2024 14:58:57 +0000 [thread overview] Message-ID: <bug-31402-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31402 Bug ID: 31402 Summary: clone (NULL, NULL, ...) clobbers %r7 register on s390{,x} Product: glibc Version: 2.40 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: jakub at redhat dot com CC: drepper.fsp at gmail dot com Target Milestone: --- Initially filed in https://gcc.gnu.org/PR113991, but it looks like a glibc bug to me. vsftpd for some strange reason does: int ret = clone(NULL, NULL, CLONE_NEWPID | CLONE_NEWIPC | SIGCHLD, NULL); My reading of glibc sources is that this results always in -1/EINVAL without invoking the syscall. Anyway, since https://sourceware.org/git/?p=glibc.git;a=commit;h=e57d8fc97b90127de4ed3e3a9cdf663667580935 if the first or second clone argument is NULL, it will return -1/EINVAL, but clobber the call-saved %r7 register. I think error: label should either lm{,g} %r6,%7 or l{,g} %r7. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-02-19 14:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-19 14:58 jakub at redhat dot com [this message] 2024-02-19 14:59 ` [Bug libc/31402] " jakub at redhat dot com 2024-02-19 15:12 ` schwab@linux-m68k.org 2024-02-19 16:30 ` sam at gentoo dot org 2024-02-20 6:50 ` stli at linux dot ibm.com 2024-02-21 21:59 ` carlos at redhat dot com 2024-02-26 12:45 ` stli at linux dot ibm.com 2024-02-27 10:16 ` stli at linux dot ibm.com
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-31402-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: 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).