[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5876D439.3090102@intel.com>
Date: Thu, 12 Jan 2017 08:56:25 +0800
From: Jike Song <jike.song@...el.com>
To: Alex Williamson <alex.williamson@...hat.com>
CC: serge@...lyn.com, linux-security-module@...r.kernel.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
kwankhede@...dia.com, kraxel@...hat.com
Subject: Re: [PATCH 1/2] capability: export has_capability
On 01/12/2017 02:47 AM, Alex Williamson wrote:
> On Thu, 22 Dec 2016 00:10:15 +0800
> Jike Song <jike.song@...el.com> 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@...hat.com>
>> Cc: Kirti Wankhede <kwankhede@...dia.com>
>> Signed-off-by: Jike Song <jike.song@...el.com>
>> ---
>> kernel/capability.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/kernel/capability.c b/kernel/capability.c
>> index 4984e1f..e2e198c 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)
>
> Are we using EXPORT_SYMBOL vs EXPORT_SYMBOL_GPL here to match the other
> exports in this file? We could use _GPL to match the expected caller
> of this.
>
Yes, I chose EXPORT_SYMBOL to match the existing exports in capability.c.
Either is good to me, of course :)
>
> Serge,
>
> Do you have any comments on this patch? I'd be happy to pull it
> through the vfio tree with an appropriate Ack. Thanks,
Guess Serge still on Xmas vocation? :)
--
Thanks,
Jike
Powered by blists - more mailing lists