From: Mike Frysinger <vapier@gentoo.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] mips: siginfo.h: add SIGSYS details [BZ #18863]
Date: Wed, 26 Aug 2015 13:10:17 -0400 [thread overview]
Message-ID: <20150826171017.GD3116@vapier> (raw)
In-Reply-To: <alpine.DEB.2.10.1508260918240.26898@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On 26 Aug 2015 09:30, Joseph Myers wrote:
> On Wed, 26 Aug 2015, Mike Frysinger wrote:
> > Linux 3.13 added SIGSYS details to siginfo_t; update glibc's copy to
> > keep in sync with it.
> >
> > 2015-08-25 Mike Frysinger <vapier@gentoo.org>
> >
> > [BZ #18863]
> > * sysdeps/unix/sysv/linux/mips/bits/siginfo.h (siginfo_t): Add _sigsys.
> > (si_call_addr): Define.
> > (si_syscall): Define.
> > (si_arch): Define.
>
> OK. CC to linux-mips because I see that the MIPS implementation of
> copy_siginfo_to_user32 doesn't handle __SI_SYS, unlike arm64 at least, so
> I suspect this won't in fact work for n32 or for o32 with a 64-bit kernel.
i'm getting reports of seccomp misbehavior on mips already which is what
started me down this glibc path. i suspect the original port was tested
against o32 kernels only.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-26 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1440563342-5411-1-git-send-email-vapier@gentoo.org>
2015-08-26 9:30 ` [PATCH] mips: siginfo.h: add SIGSYS details [BZ #18863] Joseph Myers
2015-08-26 9:30 ` Joseph Myers
2015-08-26 17:10 ` Mike Frysinger [this message]
2015-08-27 8:00 ` Markos Chandras
2015-08-27 8:00 ` Markos Chandras
2015-08-27 9:41 ` Joseph Myers
2015-08-27 9:41 ` Joseph Myers
2015-08-27 9:56 ` Markos Chandras
2015-08-27 9:56 ` Markos Chandras
2015-08-27 22:09 ` Mike Frysinger
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=20150826171017.GD3116@vapier \
--to=vapier@gentoo.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.