Re: selinux networking: sleeping functin called from invalid context in 2.6.20-rc[12]

From: Paul Moore <[email protected]>
Date: Tue, 2 Jan 2007 16:25:24 -0500

> I'm sorry I just saw this mail (mail not sent directly to me get
> shuffled off to a folder).  I agree with your patch, I think
> dropping and then re-taking the RCU lock is the best way to go,
> although I'm curious to see what others have to say.

I think this is fine too.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: selinux networking: sleeping functin called from invalid context in 2.6.20-rc[12]
    • From: "Adam J. Richter" <[email protected]>
  • Re: selinux networking: sleeping functin called from invalid context in 2.6.20-rc[12]
    • From: Paul Moore <[email protected]>

• Prev by Date: Re: [PATCH] net/core/flow.c: compare data with memcmp
• Next by Date: Re: Shrink the held_lock struct by using bitfields.
• Previous by thread: Re: selinux networking: sleeping functin called from invalid context in 2.6.20-rc[12]
• Next by thread: Re: selinux networking: sleeping functin called from invalid context in 2.6.20-rc[12]
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]