From: James Morris <jmorris@namei.org>
To: Jike Song <jike.song@intel.com>
Cc: alex.williamson@redhat.com, serge@hallyn.com,
kwankhede@nvidia.com, kraxel@redhat.com,
linux-security-module@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [v2 1/2] capability: export has_capability
Date: Fri, 13 Jan 2017 09:22:04 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1701130921560.4964@namei.org> (raw)
In-Reply-To: <1484211123-8139-2-git-send-email-jike.song@intel.com>
On Thu, 12 Jan 2017, Jike Song wrote:
> has_capability() is sometimes needed by modules to test capability
> for specified task other than current, so export it.
>
> Cc: Alex Williamson <alex.williamson@redhat.com>
> Cc: Kirti Wankhede <kwankhede@nvidia.com>
> Acked-by: Serge Hallyn <serge@hallyn.com>
> Signed-off-by: Jike Song <jike.song@intel.com>
Acked-by: James Morris <james.l.morris@oracle.com>
> ---
> kernel/capability.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/capability.c b/kernel/capability.c
> index a98e814..f97fe77 100644
> --- a/kernel/capability.c
> +++ b/kernel/capability.c
> @@ -318,6 +318,7 @@ bool has_capability(struct task_struct *t, int cap)
> {
> return has_ns_capability(t, &init_user_ns, cap);
> }
> +EXPORT_SYMBOL(has_capability);
>
> /**
> * has_ns_capability_noaudit - Does a task have a capability (unaudited)
>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2017-01-12 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 8:52 [v2 0/2] test capability for remote task Jike Song
2017-01-12 8:52 ` [v2 1/2] capability: export has_capability Jike Song
2017-01-12 22:22 ` James Morris [this message]
2017-01-12 8:52 ` [v2 2/2] vfio iommu type1: fix the testing of capability for remote task Jike Song
2017-01-12 22:22 ` James Morris
2017-01-13 6:52 ` Kirti Wankhede
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.20.1701130921560.4964@namei.org \
--to=jmorris@namei.org \
--cc=alex.williamson@redhat.com \
--cc=jike.song@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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®