From: Andreas Gruenbacher <agruenba@redhat.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>
Subject: [PATCH v2 0/2] Inode security label invalidation
Date: Sun, 4 Oct 2015 21:19:39 +0200 [thread overview]
Message-ID: <1443986381-14412-1-git-send-email-agruenba@redhat.com> (raw)
Since the first attempt at making selinux work on top of gfs2 and similar file
systems [1] was met with resistance by Christoph, here is another attempt that
doesn't require any additional inode operations, but also doesn't guarantee
full consistency of inode security labels: in case we cannot reload an invalid
label immediately, we keep using the old one.
The xattr cleanups that were part of [1] have been split off and posted
separately [2]; they seem to be okay.
Any thoughts?
Thanks,
Andreas
[1] https://lwn.net/Articles/655294/
[2] https://lkml.org/lkml/2015/10/4/137
Andreas Gruenbacher (2):
security: Add hook to invalidate inode security labels
gfs2: Invalide security labels of inodes that go invalid
fs/gfs2/glops.c | 2 ++
include/linux/lsm_hooks.h | 6 ++++++
include/linux/security.h | 5 +++++
security/security.c | 8 ++++++++
security/selinux/hooks.c | 23 +++++++++++++++++++++--
security/selinux/include/objsec.h | 3 ++-
6 files changed, 44 insertions(+), 3 deletions(-)
--
2.5.0
next reply other threads:[~2015-10-04 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 19:19 Andreas Gruenbacher [this message]
2015-10-04 19:19 ` [PATCH v2 1/2] security: Add hook to invalidate inode security labels Andreas Gruenbacher
[not found] ` <1443986381-14412-2-git-send-email-agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-05 15:08 ` Stephen Smalley
2015-10-05 21:56 ` Andreas Gruenbacher
2015-10-06 21:29 ` Stephen Smalley
2015-10-05 18:24 ` Casey Schaufler
2015-10-05 18:39 ` Andreas Gruenbacher
2015-10-04 19:19 ` [PATCH v2 2/2] gfs2: Invalide security labels of inodes that go invalid Andreas Gruenbacher
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=1443986381-14412-1-git-send-email-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).