public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ldv at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/27892] New: powerpc: scv ABI error handling fails to check IS_ERR_VALUE
Date: Thu, 20 May 2021 14:23:04 +0000	[thread overview]
Message-ID: <bug-27892-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27892
           Summary: powerpc: scv ABI error handling fails to check
                    IS_ERR_VALUE
           Product: glibc
           Version: 2.33
               URL: https://sourceware.org/pipermail/libc-alpha/2021-May/1
                    26534.html
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: ldv at sourceware dot org
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

Commit glibc-2.33~117 introduced RET_SCV macro that treats any negative value
returned by syscall via scv ABI as an error, but this is not correct.

This bug was found by strace test suite.

Proposed fix was posted by Nicholas Piggin at
https://sourceware.org/pipermail/libc-alpha/2021-May/126534.html

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

             reply	other threads:[~2021-05-20 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 14:23 ldv at sourceware dot org [this message]
2021-05-20 21:28 ` [Bug libc/27892] " tuliom at ascii dot art.br
2021-05-21 13:15 ` msc at linux dot ibm.com
2021-05-24 20:26 ` msc at linux dot ibm.com
2021-05-24 20:26 ` msc 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-27892-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).