提交 · 3b3b0e4fc15efa507b902d90cea39e496a523c3b · openeuler / raspberrypi-kernel

04 4月, 2012 1 次提交

LSM: shrink sizeof LSM specific portion of common_audit_data · 3b3b0e4f

由 Eric Paris 提交于 4月 03, 2012

Linus found that the gigantic size of the common audit data caused a big
perf hit on something as simple as running stat() in a loop. This patch
requires LSMs to declare the LSM specific portion separately rather than
doing it in a union. Thus each LSM can be responsible for shrinking their
portion and don't have to pay a penalty just because other LSMs have a
bigger space requirement.
Signed-off-by: NEric Paris <eparis@redhat.com>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

3b3b0e4f

01 4月, 2012 4 次提交

A
get rid of pointless includes of ext2_fs.h · 2f99c369
由 Al Viro 提交于 3月 23, 2012
```
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
```
2f99c369
A
selinuxfs: merge dentry allocation into sel_make_dir() · a1c2aa1e
由 Al Viro 提交于 3月 18, 2012
```
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
```
a1c2aa1e

selinux: inline avc_audit() and avc_has_perm_noaudit() into caller · cdb0f9a1

由 Linus Torvalds 提交于 3月 31, 2012

Now that all the slow-path code is gone from these functions, we can
inline them into the main caller - avc_has_perm_flags().

Now the compiler can see that 'avc' is allocated on the stack for this
case, which helps register pressure a bit.  It also actually shrinks the
total stack frame, because the stack frame that avc_has_perm_flags()
always needed (for that 'avc' allocation) is now sufficient for the
inlined functions too.

Inlining isn't bad - but mindless inlining of cold code (see the
previous commit) is.
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

cdb0f9a1

selinux: don't inline slow-path code into avc_has_perm_noaudit() · a554bea8

由 Linus Torvalds 提交于 3月 31, 2012

The selinux AVC paths remain some of the hottest (and deepest) codepaths
at filename lookup time, and we make it worse by having the slow path
cases take up I$ and stack space even when they don't trigger. Gcc
tends to always want to inline functions that are just called once -
never mind that this might make for slower and worse code in the caller.

So this tries to improve on it a bit by making the slow-path cases
explicitly separate functions that are marked noinline, causing gcc to
at least no longer allocate stack space for them unless they are
actually called. It also seems to help register allocation a tiny bit,
since gcc now doesn't take the slow case code into account.

Uninlining the slow path may also allow us to inline the remaining hot
path into the one caller that actually matters: avc_has_perm_flags().
I'll have to look at that separately, but both avc_audit() and
avc_has_perm_noaudit() are now small and lean enough that inlining them
may make sense.
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

a554bea8

29 3月, 2012 1 次提交

Remove all #inclusions of asm/system.h · 9ffc93f2

由 David Howells 提交于 3月 28, 2012

Remove all #inclusions of asm/system.h preparatory to splitting and killing
it. Performed with the following command:

perl -p -i -e 's!^#\s*include\s*<asm/system[.]h>.*\n!!' `grep -Irl '^#\s*include\s*<asm/system[.]h>' *`
Signed-off-by: NDavid Howells <dhowells@redhat.com>

9ffc93f2

26 3月, 2012 1 次提交

SELinux: selinux/xfrm.h needs net/flow.h · 778aae84

由 David Howells 提交于 3月 26, 2012

selinux/xfrm.h needs to #include net/flow.h or else suffer:

In file included from security/selinux/ss/services.c:69:0:
security/selinux/include/xfrm.h: In function 'selinux_xfrm_notify_policyload':
security/selinux/include/xfrm.h:53:14: error: 'flow_cache_genid' undeclared (first use in this function)
security/selinux/include/xfrm.h:53:14: note: each undeclared identifier is reported only once for each function it appears in
Signed-off-by: NDavid Howells <dhowells@redhat.com>

778aae84

23 3月, 2012 1 次提交

security: optimize avc_audit() common path · 48aab2f7

由 Linus Torvalds 提交于 3月 22, 2012

avc_audit() did a lot of jumping around and had a big stack frame, all
for the uncommon case.

Split up the uncommon case (which we really can't make go fast anyway)
into its own slow function, and mark the conditional branches
appropriately for the common likely case.

This causes avc_audit() to no longer show up as one of the hottest
functions on the branch profiles (the new "perf -b" thing), and makes
the cycle profiles look really nice and dense too.

The whole audit path is still annoyingly very much one of the biggest
costs of name lookup, so these things are worth optimizing for.  I wish
we could just tell people to turn it off, but realistically we do need
it: we just need to make sure that the overhead of the necessary evil is
as low as possible.
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

48aab2f7

20 2月, 2012 1 次提交

Replace the fd_sets in struct fdtable with an array of unsigned longs · 1fd36adc

由 David Howells 提交于 2月 16, 2012

Replace the fd_sets in struct fdtable with an array of unsigned longs and then
use the standard non-atomic bit operations rather than the FD_* macros.

This:

 (1) Removes the abuses of struct fd_set:

     (a) Since we don't want to allocate a full fd_set the vast majority of the
     	 time, we actually, in effect, just allocate a just-big-enough array of
     	 unsigned longs and cast it to an fd_set type - so why bother with the
     	 fd_set at all?

     (b) Some places outside of the core fdtable handling code (such as
     	 SELinux) want to look inside the array of unsigned longs hidden inside
     	 the fd_set struct for more efficient iteration over the entire set.

 (2) Eliminates the use of FD_*() macros in the kernel completely.

 (3) Permits the __FD_*() macros to be deleted entirely where not exposed to
     userspace.
Signed-off-by: NDavid Howells <dhowells@redhat.com>
Link: http://lkml.kernel.org/r/20120216174954.23314.48147.stgit@warthog.procyon.org.ukSigned-off-by: NH. Peter Anvin <hpa@zytor.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>

1fd36adc

14 2月, 2012 1 次提交

security: trim security.h · 40401530

由 Al Viro 提交于 2月 13, 2012

Trim security.h
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
Signed-off-by: NJames Morris <jmorris@namei.org>

40401530

07 1月, 2012 1 次提交
- A
  vfs: prefer ->dentry->d_sb to ->mnt->mnt_sb · d8c9584e
  由 Al Viro 提交于 12月 07, 2011
```
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
```
  d8c9584e
06 1月, 2012 9 次提交

security: remove the security_netlink_recv hook as it is equivalent to capable() · fd778461

由 Eric Paris 提交于 1月 03, 2012

Once upon a time netlink was not sync and we had to get the effective
capabilities from the skb that was being received.  Today we instead get
the capabilities from the current task.  This has rendered the entire
purpose of the hook moot as it is now functionally equivalent to the
capable() call.
Signed-off-by: NEric Paris <eparis@redhat.com>

fd778461

ptrace: do not audit capability check when outputing /proc/pid/stat · 69f594a3

由 Eric Paris 提交于 1月 03, 2012

Reading /proc/pid/stat of another process checks if one has ptrace permissions
on that process. If one does have permissions it outputs some data about the
process which might have security and attack implications. If the current
task does not have ptrace permissions the read still works, but those fields
are filled with inocuous (0) values. Since this check and a subsequent denial
is not a violation of the security policy we should not audit such denials.

This can be quite useful to removing ptrace broadly across a system without
flooding the logs when ps is run or something which harmlessly walks proc.
Signed-off-by: NEric Paris <eparis@redhat.com>
Acked-by: NSerge E. Hallyn <serge.hallyn@canonical.com>

69f594a3

capabilities: remove the task from capable LSM hook entirely · 6a9de491

由 Eric Paris 提交于 1月 03, 2012

The capabilities framework is based around credentials, not necessarily the
current task. Yet we still passed the current task down into LSMs from the
security_capable() LSM hook as if it was a meaningful portion of the security
decision. This patch removes the 'generic' passing of current and instead
forces individual LSMs to use current explicitly if they think it is
appropriate. In our case those LSMs are SELinux and AppArmor.

I believe the AppArmor use of current is incorrect, but that is wholely
unrelated to this patch. This patch does not change what AppArmor does, it
just makes it clear in the AppArmor code that it is doing it.

The SELinux code still uses current in it's audit message, which may also be
wrong and needs further investigation. Again this is NOT a change, it may
have always been wrong, this patch just makes it clear what is happening.
Signed-off-by: NEric Paris <eparis@redhat.com>

6a9de491

selinux: sparse fix: fix several warnings in the security server cod · 2653812e