public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29770] New: prctl does not match manual page ABI on powerpc64le-linux-gnu
Date: Thu, 10 Nov 2022 08:36:56 +0000	[thread overview]
Message-ID: <bug-29770-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29770

            Bug ID: 29770
           Summary: prctl does not match manual page ABI on
                    powerpc64le-linux-gnu
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: fweimer at redhat dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---
            Target: powerpc64le-linux-gnu
             Flags: security-

On powerpc64le-linux-gnu, since

commit ff026950e280bc3e9487b41b460fb31bc5b57721
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Thu Apr 30 10:42:43 2020 -0700

    Add a C wrapper for prctl [BZ #25896]

    Add a C wrapper to pass arguments in

    /* Control process execution.  */
    extern int prctl (int __option, ...) __THROW;

    to prctl syscall:

    extern int prctl (int, unsigned long int, unsigned long int,
                      unsigned long int, unsigned long int);

the glibc ABI no longer matches what is documented in the manual page, which
mentions the second prototype only. Calls through the non-variadic prototype do
not set up a parameter save area, and use of the area by the glibc
implementation corrupts the stack in the caller.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-11-10  8:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  8:36 fweimer at redhat dot com [this message]
2022-11-10  8:44 ` [Bug libc/29770] " fweimer at redhat dot com
2022-11-10  8:45 ` sam at gentoo dot org
2022-11-10 16:28 ` fweimer at redhat dot com
2024-02-02 18:38 ` fweimer at redhat dot com
2024-02-02 18:46 ` fweimer at redhat dot com
2024-02-02 21:28 ` fweimer at redhat dot com
2024-02-02 21:31 ` fweimer at redhat dot com
2024-02-05  9:37 ` fweimer at redhat dot com
2024-02-17  8:17 ` cvs-commit at gcc dot gnu.org
2024-02-17  8:27 ` fweimer at redhat dot 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-29770-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).