linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Graziano <david.graziano@rockwellcollins.com>
To: linux-security-module@vger.kernel.org, paul@paul-moore.com
Cc: agruenba@redhat.com, hch@infradead.org, linux-mm@kvack.org,
	sds@tycho.nsa.gov, linux-kernel@vger.kernel.org,
	David Graziano <david.graziano@rockwellcollins.com>
Subject: [PATCH v4 0/3] initxattr callback update for mqueue xattr support
Date: Thu,  5 Jan 2017 16:03:40 -0600	[thread overview]
Message-ID: <1483653823-22018-1-git-send-email-david.graziano@rockwellcollins.com> (raw)

This patchset is for implementing extended attribute support within the 
POSIX message queue (mqueue) file system. This is needed so that the 
security.selinux extended attribute can be set via a SELinux named type 
transition on file inodes created within the filesystem. I needed to 
write a selinux policy for a set of custom applications that use mqueues 
for their IPC. The mqueues are created by one application and we needed 
a way for selinux to enforce which of the other application are able to 
read/write to each individual queue. Uniquely labelling them based on the 
application that created them and the filename seemed to be our best 
solution as it’s an embedded system and we don’t have restorecond to 
handle any relabeling.

This series is a result of feedback from the v2 mqueue patch 
( http://marc.info/?l=linux-kernel&m=147855351826081&w=2 ) which 
duplicated the shmem_initxattrs() function for the mqueue file system. 
This patcheset creates a common simple_xattr_initxattrs() function that 
can be used by multiple virtual file systems to handle extended attribute 
initialization via LSM callback. simple_xattr_initxattrs() is an updated 
version of shmem_initxattrs(). As part of the this series both shmem and 
mqueue are updated to use the new common initxattrs function. 

Changes v3 -> v4:
 - fix uninitialized variable in mqueue patch (3/3)

Changes v2 -> v3:
 - creates new simple_xattr_initxattrs() function
 - updates shmem to use new callback function
 - updates mqueue to use new callback function

Changes v1 -> v2:
 - formatting/commit message


David Graziano (3):
  xattr: add simple initxattrs function
  shmem: use simple initxattrs callback
  mqueue: Implement generic xattr support

 fs/xattr.c            | 39 +++++++++++++++++++++++++++++++++++++
 include/linux/xattr.h |  3 +++
 ipc/mqueue.c          | 16 ++++++++++++++++
 mm/shmem.c            | 53 ++++++++++++---------------------------------------
 4 files changed, 70 insertions(+), 41 deletions(-)

-- 
1.9.1

             reply	other threads:[~2017-01-05 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 22:03 David Graziano [this message]
2017-01-05 22:03 ` [PATCH v4 1/3] xattr: add simple initxattrs function David Graziano
2017-01-08  9:55   ` Christoph Hellwig
2017-01-09 15:41     ` David Graziano
2017-01-05 22:03 ` [PATCH v4 2/3] shmem: use simple initxattrs callback David Graziano
2017-01-05 22:03 ` [PATCH v4 3/3] mqueue: Implement generic xattr support David Graziano

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=1483653823-22018-1-git-send-email-david.graziano@rockwellcollins.com \
    --to=david.graziano@rockwellcollins.com \
    --cc=agruenba@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=sds@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;
as well as URLs for NNTP newsgroup(s).