From: Hugo Mills <hugo@carfax.org.uk>
To: Alex <alex@bpmit.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: SELinux inode size gotcha in btrfs.
Date: Mon, 27 Feb 2012 23:09:05 +0000 [thread overview]
Message-ID: <20120227230904.GC4481@carfax.org.uk> (raw)
In-Reply-To: <loom.20120227T210703-631@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
On Mon, Feb 27, 2012 at 10:18:55PM +0000, Alex wrote:
> I've come across the 'gotcha' in XFS where the inode size defaults to 256 [1]
> whereas for SELinux the attributes play better when you initialise it at
> creation to 512.
A btrfs inode structure is 136 bytes in size. xattrs and any inline
file data are separate from the inode structure, stored with
additional keys in the FS tree (which means that they're quite likely
to appear in the same page, as the inode data, but not guaranteed).
> From my reading of the btrfs specs [2] it doesn't look like you'll get caught
> with that as the inodes "will not contain embedded file data or extended
> attribute data. These things are stored in other item types."
>
> Have I read that right? I've seen xattr bugs patches etc but nothing that would
> hit the SE Linux domain.
It's not clear from looking at the gentoo doc what the problem
actually is with different inode sizes... Without some kind of
indication what the issue really is, it's kind of hard to say how this
might affect btrfs.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- The enemy have elected for Death by Powerpoint. That's what ---
they shall get. -- gdb
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2012-02-27 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 22:18 SELinux inode size gotcha in btrfs Alex
2012-02-27 23:09 ` Hugo Mills [this message]
2012-02-27 23:17 ` David Sterba
2012-02-28 11:30 ` Alex
2012-02-28 11:37 ` Hugo Mills
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=20120227230904.GC4481@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=alex@bpmit.com \
--cc=linux-btrfs@vger.kernel.org \
/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).