From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] xfstests: mount other filesystems with selinux context as well
Date: Wed, 25 Jan 2012 15:28:12 -0600 [thread overview]
Message-ID: <4F2073EC.80208@sandeen.net> (raw)
In-Reply-To: <20120125211438.GA11821@infradead.org>
On 1/25/12 3:14 PM, Christoph Hellwig wrote:
> On Wed, Jan 25, 2012 at 03:11:39PM -0600, Eric Sandeen wrote:
>> For some reason, non-xfs filesystems aren't getting mounted with
>> the selinux context; perhaps because none of the xattr tests used
>> to work on anything but xfs?
>>
>> Anyway, 062 fails for extN unless we mount with the fs-wide
>> context.
>>
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>> ---
>>
>> ps: eparis says this should work for NFS as well, let's go for
>> it and if infrequently tested filesystems have trouble we can
>> exclude them as necessary.
>
> Verifying that assumption isn't hard, please do it.
>
# mount -t nfs -o context=system_u:object_r:nfs_t:s0 localhost:/mnt/export /mnt/test
# grep /mnt/export /proc/mounts
localhost:/mnt/export /mnt/test nfs4 rw,context=system_u:object_r:nfs_t:s0,relatime,vers=4,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=127.0.0.1,minorversion=0,local_lock=none,addr=127.0.0.1 0 0
next prev parent reply other threads:[~2012-01-25 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 17:50 [PATCH] xfstests: mount other filesystems with selinux context as well Eric Sandeen
2011-11-28 11:02 ` Christoph Hellwig
2012-01-19 18:37 ` Eric Sandeen
2012-01-24 17:45 ` Christoph Hellwig
2012-01-25 21:11 ` [PATCH V2] " Eric Sandeen
2012-01-25 21:14 ` Christoph Hellwig
2012-01-25 21:28 ` Eric Sandeen [this message]
2012-01-27 11:00 ` Christoph Hellwig
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=4F2073EC.80208@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.com \
/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).