Re: [AppArmor 40/41] AppArmor: all the rest

2007-04-12 Thread Al Viro
On Thu, Apr 12, 2007 at 11:32:00AM +0100, Al Viro wrote: > On Thu, Apr 12, 2007 at 02:08:49AM -0700, [EMAIL PROTECTED] wrote: > > + } else if (profile1 > profile2) { > > + /* profile1 cannot be NULL here. */ > > + spin_lock_irqsave(&profile1->lock, profile1->int_flags); > > +

Re: [AppArmor 40/41] AppArmor: all the rest

2007-04-12 Thread Al Viro
On Thu, Apr 12, 2007 at 02:08:49AM -0700, [EMAIL PROTECTED] wrote: > + } else if (profile1 > profile2) { > + /* profile1 cannot be NULL here. */ > + spin_lock_irqsave(&profile1->lock, profile1->int_flags); > + if (profile2) > + spin_lock(&

[AppArmor 40/41] AppArmor: all the rest

2007-04-12 Thread jjohansen
All the things that didn't nicely fit in a category on their own: kbuild code, declararions and inline functions, /sys/kernel/security/apparmor filesystem for controlling apparmor from user space, profile list functions, locking documentation, /proc/$pid/task/$tid/attr/current access. Signed-off-b