Re: Problem with accessing namespace_sem from LSM.

On Tue, Nov 06, 2007 at 01:00:41PM +0900, Tetsuo Handa wrote:
> Hello.
> 
> I found that accessing namespace_sem from security_inode_create()
> causes lockdep warning when compiled with CONFIG_PROVE_LOCKING=y .

Any code except VFS internals has no business using it at all and doesn't
do that in mainline either.  I'd start looking for design bugs in whatever
code you have using it first.

-
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/

---

• Follow-Ups:
  • Re: Problem with accessing namespace_sem from LSM.
    • From: Tetsuo Handa <[email protected]>

• References:
  • Problem with accessing namespace_sem from LSM.
    • From: Tetsuo Handa <[email protected]>

• Prev by Date: Re: [PATCH] Smackv10: Smack rules grammar + their stateful parser
• Next by Date: Re: 2.6.24-rc1-git15 Kernel build fails on powerpc - Unrecognized opcode: `dssall'
• Previous by thread: Re: Problem with accessing namespace_sem from LSM.
• Next by thread: Re: Problem with accessing namespace_sem from LSM.
• 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]