From: Linus Torvalds <torvalds@linux-foundation.org>
To: Eric Paris <eparis@redhat.com>
Cc: sds@tycho.nsa.gov, linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH 2/2] SELinux: cache inode checks inside struct inode
Date: Tue, 4 Jun 2013 06:31:30 +0900 (PWT) [thread overview]
Message-ID: <alpine.LFD.2.03.1306040628420.25797@pixel.linux-foundation.org> (raw)
In-Reply-To: <1370285941-18367-2-git-send-email-eparis@redhat.com>
On Mon, 3 Jun 2013, Eric Paris wrote:
>
> #ifdef CONFIG_SECURITY
> + seqcount_t i_security_seqcount;
> + u32 i_last_task_sid;
> + u32 i_last_granting;
> + u32 i_last_perms;
> + u32 i_audit_allow;
> void *i_security;
> #endif
This is much too big. I was really hoping for "another word that the
security layer can use" or similar.
Something this big would be acceptable if it would be a *generic* security
cache, and others could use it too, and would avoid ever actually calling
into any security layer at all (ie we could do the checks entirely at the
VFS layer). Then it would be fine. But for just the fact that SELinux is
too slow? No.
Linus
next prev parent reply other threads:[~2013-06-03 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 18:59 [RFC PATCH 1/2] selinux: merge selinux_inode_permission and inode_has_perm Eric Paris
2013-06-03 18:59 ` [RFC PATCH 2/2] SELinux: cache inode checks inside struct inode Eric Paris
2013-06-03 20:26 ` Casey Schaufler
2013-06-04 1:00 ` Casey Schaufler
2013-06-03 21:31 ` Linus Torvalds [this message]
2013-06-03 23:18 ` Eric Paris
2013-06-04 2:52 ` Casey Schaufler
2013-06-03 19:33 ` [RFC PATCH 1/2] selinux: merge selinux_inode_permission and inode_has_perm Eric Paris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.03.1306040628420.25797@pixel.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox