mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: linux-security-module@vger.kernel.org,
	Serge Hallyn <serge@hallyn.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] capabilities: add description for CAP_SETFCAP
Date: Fri, 1 May 2020 13:51:10 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.2005011350590.29679@namei.org> (raw)
In-Reply-To: <20200428085816.GD15547@stefanha-x1.localdomain>

On Tue, 28 Apr 2020, Stefan Hajnoczi wrote:

> On Tue, Apr 14, 2020 at 04:49:45PM +0100, Stefan Hajnoczi wrote:
> > Document the purpose of CAP_SETFCAP.  For some reason this capability
> > had no description while the others did.
> > 
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > ---
> >  include/uapi/linux/capability.h | 2 ++
> >  1 file changed, 2 insertions(+)
> 
> Ping?

Please resend and I'll add it to my tree.

> 
> > diff --git a/include/uapi/linux/capability.h b/include/uapi/linux/capability.h
> > index 272dc69fa080..7288f0ad44af 100644
> > --- a/include/uapi/linux/capability.h
> > +++ b/include/uapi/linux/capability.h
> > @@ -332,6 +332,8 @@ struct vfs_ns_cap_data {
> >  
> >  #define CAP_AUDIT_CONTROL    30
> >  
> > +/* Set or remove capabilities on files */
> > +
> >  #define CAP_SETFCAP	     31
> >  
> >  /* Override MAC access.
> > -- 
> > 2.25.1
> > 
> 

-- 
James Morris
<jmorris@namei.org>


      reply	other threads:[~2020-05-01  3:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 15:49 Stefan Hajnoczi
2020-04-28  8:58 ` Stefan Hajnoczi
2020-05-01  3:51   ` James Morris [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=alpine.LRH.2.21.2005011350590.29679@namei.org \
    --to=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=stefanha@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

all inboxes | Powered by JetHome®