Trinity fuzzer tool discussions
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Dave Jones <davej@redhat.com>
Cc: trinity@vger.kernel.org
Subject: Re: [PATCH] Compat fixes for DRM & prctl()
Date: Mon, 26 May 2014 13:06:29 +1000	[thread overview]
Message-ID: <1401073589.3839.2.camel@concordia> (raw)
In-Reply-To: <20140524004818.GA7139@redhat.com>

On Fri, 2014-05-23 at 20:48 -0400, Dave Jones wrote:
> On Fri, May 23, 2014 at 07:09:25PM +1000, Michael Ellerman wrote:
>  > ---
>  >  include/compat.h | 9 +++++++++
>  >  ioctls/drm.c     | 2 ++
>  >  2 files changed, 11 insertions(+)
>  > 
>  > diff --git a/include/compat.h b/include/compat.h
>  > index 51f0936..8bdaf92 100644
>  > --- a/include/compat.h
>  > +++ b/include/compat.h
>  > @@ -257,10 +257,19 @@ enum {
>  >  
>  >  #ifndef PR_SET_MM
>  >  #define PR_SET_MM               35
>  > +#endif
>  > +
>  > +#ifndef PR_SET_CHILD_SUBREAPER
>  >  #define PR_SET_CHILD_SUBREAPER  36
>  >  #define PR_GET_CHILD_SUBREAPER  37
>  > +#endif
>  > +
>  > +#ifndef PR_SET_NO_NEW_PRIVS
>  >  #define PR_SET_NO_NEW_PRIVS     38
>  >  #define PR_GET_NO_NEW_PRIVS     39
>  > +#endif
>  > +
>  > +#ifndef PR_GET_TID_ADDRESS
>  >  #define PR_GET_TID_ADDRESS      40
>  >  #endif
> 
> I applied Vinson's variant of this, which I think should be
> sufficient, because iirc, those all got added at the same time.
> Can you send a follow up if needed ?

OK. I had a quick look and it looked like some were added separately, but
Vinson's patch builds for me so that's fine.

> I edited your diff and applied the DRM part separately.

Thanks.

cheers


      reply	other threads:[~2014-05-26  3:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  9:09 [PATCH] Compat fixes for DRM & prctl() Michael Ellerman
2014-05-24  0:48 ` Dave Jones
2014-05-26  3:06   ` Michael Ellerman [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=1401073589.3839.2.camel@concordia \
    --to=mpe@ellerman.id.au \
    --cc=davej@redhat.com \
    --cc=trinity@vger.kernel.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