Re: Problem with accessing namespace_sem from LSM.

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?
I think security_inode_create() is a part of VFS internals
because it is called from vfs_create().

Regards.

-
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: Christoph Hellwig <[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]>

Prev by Date: Re: [PATCH] Smackv10: Smack rules grammar + their stateful parser
Next by Date: Re: 2.6.23: no more free evdev devices - evdev leak?
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]