public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msc at linux dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/27892] powerpc: scv ABI error handling fails to check IS_ERR_VALUE
Date: Mon, 24 May 2021 20:26:22 +0000 [thread overview]
Message-ID: <bug-27892-131-JaQp9IzHhj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27892-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27892
Matheus Castanho <msc at linux dot ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Matheus Castanho <msc at linux dot ibm.com> ---
Issue fixed on master for glibc 2.34:
commit 7de36744ee1325f35d3fe0ca079dd33c40b12267
Author: Nicholas Piggin <npiggin@gmail.com>
Date: Thu May 20 11:00:36 2021 -0300
powerpc: Fix handling of scv return error codes [BZ #27892]
When using scv for templated ASM syscalls, current code interprets any
negative return value as error, but the only valid error codes are in
the range -4095..-1 according to the ABI.
This commit also fixes 'signal.gen.test' strace test, where the issue
was first identified.
Reviewed-by: Matheus Castanho <msc@linux.ibm.com>
This patch was also backported to 2.33 by commit
0ef0e6de7fdfa18328b09ba2afb4f0112d4bdab4.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-24 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 14:23 [Bug libc/27892] New: " ldv at sourceware dot org
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 [this message]
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-JaQp9IzHhj@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).