Re: Problem with accessing namespace_sem from LSM.

On Tue, Nov 06, 2007 at 11:52:40PM +0900, Tetsuo Handa wrote:
> Hello.
> 
> Christoph Hellwig wrote:
> > 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.
> Isn't security_inode_create() a part of VFS internals?

It's not.  security_inode_create is part of the LSM infrastructure, and
the actual methods are part of security modules and definitively not
VFS internals.
-
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]>
  • Re: Problem with accessing namespace_sem from LSM.
    • From: Christoph Hellwig <[email protected]>
  • Re: Problem with accessing namespace_sem from LSM.
    • From: Tetsuo Handa <[email protected]>

• Prev by Date: Re: [PATCH] frv: Remove bogus NO_IRQ = -1 define
• Next by Date: Re: [PATCH] virtio config_ops refactoring
• 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]