From: Russell Coker <russell@coker.com.au>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: SELinux on btrfs
Date: Fri, 2 May 2014 11:51:05 +1000 [thread overview]
Message-ID: <201405021151.06080.russell@coker.com.au> (raw)
In-Reply-To: <1334991E-DB91-4AA8-AF51-E11C881AB8C2@colorremedies.com>
On Thu, 1 May 2014, Chris Murphy <lists@colorremedies.com> wrote:
> That has not been my experience. I changed /boot files to have the wrong
> selinux labels, set .autorelabel, rebooted, and those files were fixed
> despite /boot being a mount point for a btrfs subvolume named boot located
> at the top level of the file system, and mounted with an fstab using
> subvol=boot option.
>
> I can see how unmounted subvolumes won't be visible to any scripts or even
> restorecon, so maybe that's what's being referred to?
Yes I believe that the problem is anything that looks like a separate
filesystem to stat() but doesn't have an entry in /proc/mounts. So if you
mount the subvols separately then there's no problem.
Another thing is that if the subvols aren't needed for booting (IE /home) then
you can just manually label them either before or after the autorelabel boot.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2014-05-02 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 16:15 SELinux on btrfs Chris Murphy
2014-04-30 8:01 ` Russell Coker
2014-04-30 16:04 ` Chris Murphy
2014-05-02 1:51 ` Russell Coker [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-01 14:50 Michael Schuerig
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=201405021151.06080.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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