Re: [PATCH 01/13] AppArmor: misc. base functions and defines

From: Pekka Enberg
Date: Fri Jul 30 2010 - 11:01:48 EST

On Fri, Jul 30, 2010 at 5:24 PM, Changli Gao <xiaosuo@xxxxxxxxx> wrote:
> On Fri, Jul 30, 2010 at 6:53 PM, Pekka Enberg <penberg@xxxxxxxxxxxxxx> wrote:
>> On Fri, Jul 30, 2010 at 1:01 PM, John Johansen
>>> vfree can sleep, and skipping the schedule_work parts won't work for
>>> apparmor as many of these allocations are being freed via rcu callbacks
>>> as most of our object life cycles are dependent on cred refcounting.
>> Can someone point me to where vfree() actually sleeps? I'm unable to
>> find the exact spot.
> . vfree ->
> __vunmap, vunmap -> __vunmap, and there is a might_sleep() function in
> vunmap.

Yes, but that doesn't answer my question. Where's the actual call-site
that can sleep? I can't find it!

> BTW: I'll respin the kvmalloc patch later.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at