public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: libc-alpha@sourceware.org
Cc: Andreas Jaeger <aj@suse.com>, libc-ports@sources.redhat.com
Subject: Re: Sync with Linux 3.5 v2
Date: Wed, 25 Jul 2012 15:44:00 -0000	[thread overview]
Message-ID: <201207251145.29505.vapier@gentoo.org> (raw)
In-Reply-To: <hofw8gosj9.fsf@byrd.suse.de>

[-- Attachment #1: Type: Text/Plain, Size: 1031 bytes --]

On Wednesday 25 July 2012 09:54:18 Andreas Jaeger wrote:
> For Changelog.ia64:
> 2012-07-25  Andreas Jaeger  <aj@suse.de>
> 
> 	* sysdeps/unix/sysv/linux/ia64/sys/ptrace.h (__ptrace_eventcodes):
> 	Add new value PTRACE_EVENT_SECCOMP from Linux 3.5.
> 	(__ptrace_setoptions): Add new value PTRACE_O_TRACESECCOMP, adjust
> 	PTRACE_O_MASK.
> ...
> --- a/ports/sysdeps/unix/sysv/linux/ia64/sys/ptrace.h
> +++ b/ports/sysdeps/unix/sysv/linux/ia64/sys/ptrace.h
> 
>  /* Options set using PTRACE_SETOPTIONS.  */
> -enum __ptrace_setoptions {
> +enum __ptrace_setoptions
> +{
>    PTRACE_O_TRACESYSGOOD	= 0x00000001,
>    PTRACE_O_TRACEFORK	= 0x00000002,
>    PTRACE_O_TRACEVFORK   = 0x00000004,
>    PTRACE_O_TRACECLONE	= 0x00000008,
>    PTRACE_O_TRACEEXEC	= 0x00000010,
>    PTRACE_O_TRACEVFORKDONE = 0x00000020,
> -  PTRACE_O_TRACEEXIT	= 0x00000040,
> -  PTRACE_O_MASK		= 0x0000007f
> +  PTRACE_O_TRACESECCOMP = 0x00000080,
> +  PTRACE_O_MASK		= 0x000000ff
>  };

did you mean to delete TRACEEXIT ?
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-07-25 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 13:54 Andreas Jaeger
2012-07-25 15:44 ` Mike Frysinger [this message]

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=201207251145.29505.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=aj@suse.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sources.redhat.com \
    /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).