<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/security/apparmor/capability.c, branch v3.6-rc6</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/security/apparmor/capability.c?h=v3.6-rc6</id>
<link rel='self' href='https://git.amat.us/linux/atom/security/apparmor/capability.c?h=v3.6-rc6'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-04-09T16:23:04Z</updated>
<entry>
<title>LSM: do not initialize common_audit_data to 0</title>
<updated>2012-04-09T16:23:04Z</updated>
<author>
<name>Eric Paris</name>
<email>eparis@redhat.com</email>
</author>
<published>2012-04-04T19:01:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=50c205f5e5c2e2af002fd4ef537ded79b90b1b56'/>
<id>urn:sha1:50c205f5e5c2e2af002fd4ef537ded79b90b1b56</id>
<content type='text'>
It isn't needed.  If you don't set the type of the data associated with
that type it is a pretty obvious programming bug.  So why waste the cycles?

Signed-off-by: Eric Paris &lt;eparis@redhat.com&gt;
</content>
</entry>
<entry>
<title>apparmor: move task from common_audit_data to apparmor_audit_data</title>
<updated>2012-04-09T16:23:02Z</updated>
<author>
<name>Eric Paris</name>
<email>eparis@redhat.com</email>
</author>
<published>2012-04-04T19:01:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0972c74ecba4878baa5f97bb78b242c0eefacfb6'/>
<id>urn:sha1:0972c74ecba4878baa5f97bb78b242c0eefacfb6</id>
<content type='text'>
apparmor is the only LSM that uses the common_audit_data tsk field.
Instead of making all LSMs pay for the stack space move the aa usage into
the apparmor_audit_data.

Signed-off-by: Eric Paris &lt;eparis@redhat.com&gt;
</content>
</entry>
<entry>
<title>LSM: remove the COMMON_AUDIT_DATA_INIT type expansion</title>
<updated>2012-04-09T16:23:01Z</updated>
<author>
<name>Eric Paris</name>
<email>eparis@redhat.com</email>
</author>
<published>2012-04-04T19:01:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bd5e50f9c1c71daac273fa586424f07205f6b13b'/>
<id>urn:sha1:bd5e50f9c1c71daac273fa586424f07205f6b13b</id>
<content type='text'>
Just open code it so grep on the source code works better.

Signed-off-by: Eric Paris &lt;eparis@redhat.com&gt;
</content>
</entry>
<entry>
<title>LSM: shrink sizeof LSM specific portion of common_audit_data</title>
<updated>2012-04-03T16:48:40Z</updated>
<author>
<name>Eric Paris</name>
<email>eparis@redhat.com</email>
</author>
<published>2012-04-03T16:37:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3b3b0e4fc15efa507b902d90cea39e496a523c3b'/>
<id>urn:sha1:3b3b0e4fc15efa507b902d90cea39e496a523c3b</id>
<content type='text'>
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: Eric Paris &lt;eparis@redhat.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>AppArmor: mediation of non file objects</title>
<updated>2010-08-02T05:38:35Z</updated>
<author>
<name>John Johansen</name>
<email>john.johansen@canonical.com</email>
</author>
<published>2010-07-29T21:48:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0ed3b28ab8bf460a3a026f3f1782bf4c53840184'/>
<id>urn:sha1:0ed3b28ab8bf460a3a026f3f1782bf4c53840184</id>
<content type='text'>
ipc:
AppArmor ipc is currently limited to mediation done by file mediation
and basic ptrace tests.  Improved mediation is a wip.

rlimits:
AppArmor provides basic abilities to set and control rlimits at
a per profile level.  Only resources specified in a profile are controled
or set.  AppArmor rules set the hard limit to a value &lt;= to the current
hard limit (ie. they can not currently raise hard limits), and if
necessary will lower the soft limit to the new hard limit value.

AppArmor does not track resource limits to reset them when a profile
is left so that children processes inherit the limits set by the
parent even if they are not confined by the same profile.

Capabilities:  AppArmor provides a per profile mask of capabilities,
that will further restrict.

Signed-off-by: John Johansen &lt;john.johansen@canonical.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
</content>
</entry>
</feed>
