From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Chris Mason <clm@fb.com>
Cc: Eric Sandeen <sandeen@redhat.com>, <linux-btrfs@vger.kernel.org>,
<guaneryu@gmail.com>
Subject: Re: [PATCH] btrfs: Make btrfs handle security mount options internally to avoid losing security label.
Date: Tue, 7 Oct 2014 09:01:09 +0800 [thread overview]
Message-ID: <54333B55.2010304@cn.fujitsu.com> (raw)
In-Reply-To: <1412601999.31886.2@mail.thefacebook.com>
-------- Original Message --------
Subject: Re: [PATCH] btrfs: Make btrfs handle security mount options
internally to avoid losing security label.
From: Chris Mason <clm@fb.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Date: 2014年10月06日 21:26
> On Sun, Oct 5, 2014 at 11:02 PM, Qu Wenruo <quwenruo@cn.fujitsu.com>
> wrote:
>>
>>>
>>> I don't think that my "wish" should disallow your patch.
>>>
>>> For the problem I was looking at, I think the only way forward would
>>> require
>>> some significant selinux modification, and treating a subvol root
>>> essentially
>>> like a superblock.
>>>
>>> So ... don't let me slow you down, at least for now. ;)
>>>
>>> -Eric
>>>
>> To Chris, any other comment?
>
> It looks good to me, and I have it queued up here in testing.
>
> -chris
>
>
>
Thanks a lot.
Qu
next prev parent reply other threads:[~2014-10-07 1:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 5:40 [PATCH] btrfs: Make btrfs handle security mount options internally to avoid losing security label Qu Wenruo
2014-09-23 12:49 ` Chris Mason
2014-09-23 18:51 ` Eric Sandeen
2014-09-24 0:31 ` Qu Wenruo
2014-09-24 3:33 ` Eric Sandeen
2014-09-24 3:43 ` Qu Wenruo
2014-10-06 3:02 ` Qu Wenruo
2014-10-06 13:26 ` Chris Mason
2014-10-07 1:01 ` Qu Wenruo [this message]
2014-10-06 13:29 ` Josef Bacik
2014-10-06 13:38 ` Eryu Guan
2014-10-07 1:03 ` Qu Wenruo
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=54333B55.2010304@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=clm@fb.com \
--cc=guaneryu@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandeen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.