Re: [PATCH linux-next] SELinux: security_load_policy: Silence frame-larger-thanwarning

[Tim Gardner]

On 11/19/2013 02:38 PM, Paul Moore wrote:
> On Thursday, November 14, 2013 03:04:51 PM Tim Gardner wrote:
>> Dynamically allocate a couple of the larger stack variables in order to
>> reduce the stack footprint below 1024. gcc-4.8
>>
>> security/selinux/ss/services.c: In function 'security_load_policy':
>> security/selinux/ss/services.c:1964:1: warning: the frame size of 1104 bytes
>> is larger than 1024 bytes [-Wframe-larger-than=] }
>>
>> Also silence a couple of checkpatch warnings at the same time.
>>
>> WARNING: sizeof policydb should be sizeof(policydb)
>> +	memcpy(oldpolicydb, &policydb, sizeof policydb);
>>
>> WARNING: sizeof policydb should be sizeof(policydb)
>> +	memcpy(&policydb, newpolicydb, sizeof policydb);
>>
>> Cc: Stephen Smalley <sds@xxxxxxxxxxxxx>
>> Cc: James Morris <james.l.morris@xxxxxxxxxx>
>> Cc: Eric Paris <eparis@xxxxxxxxxxxxxx>
>> Signed-off-by: Tim Gardner <tim.gardner@xxxxxxxxxxxxx>
>> ---
>>  security/selinux/ss/services.c |   54 ++++++++++++++++++++++--------------
>>  1 file changed, 32 insertions(+), 22 deletions(-)
> 
> Applied, thanks.  It will be pushed to my next tree once -rc1 is released.
> 
> In the future, please send SELinux patches to the SELinux mailing list.
> 

It is difficult to know where to send a patch for every subsystem. I've
been using the get_maintainer.pl script, so perhaps the info in
MAINTAINERS is stale ? I'm open to suggestions.

$: scripts/get_maintainer.pl -f security/selinux/ss/services.c
Stephen Smalley <sds@xxxxxxxxxxxxx> (supporter:SELINUX SECURITY...)
James Morris <james.l.morris@xxxxxxxxxx> (supporter:SELINUX SECURITY...)
Eric Paris <eparis@xxxxxxxxxxxxxx> (supporter:SELINUX SECURITY...)
linux-security-module@xxxxxxxxxxxxxxx (open list:SECURITY SUBSYSTEM)
linux-kernel@xxxxxxxxxxxxxxx (open list)

rtg
-- 
Tim Gardner tim.gardner@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/