From: Alex <alex@bpmit.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: SELinux inode size gotcha in btrfs.
Date: Tue, 28 Feb 2012 11:30:26 +0000 (UTC) [thread overview]
Message-ID: <loom.20120228T122833-822@post.gmane.org> (raw)
In-Reply-To: 20120227231749.GR1046@twin.jikos.cz
David Sterba <dave <at> jikos.cz> writes:
>
> That's right. Inode represented as btrfs_inode_item does not contain any
> xattr fields, they're stored independently as a btrfs_dir_item of type
> BTRFS_FT_XATTR . Due to the way the b-tree keys are built, the xattr
> item key should be stored near the inode item key, that's for the tree
> search side. The xattr data are always stored inline in the b-tree leaf.
>
Thank you David and Hugo,
My bad on three counts:
1) My courtesy close seems to have gone missing.
Sorry and thank you for replying.
2) I, perhaps, should have pointed to
https://wiki.debian.org/SELinux/Setup#Prerequisites
_.28kernel_and_filesystems.29
which gives a better explanation.
3) Made it clear that I wasn't attacking
XFS, It's my fs of (non /boot) choice
for some years now; I'm exploring SELinux
(after the recent Linux conf au 2012
talk) and know I have used inode size defaults
for my xfs init back in the day!
Best
Al.
next prev parent reply other threads:[~2012-02-28 11:30 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
2012-02-27 23:17 ` David Sterba
2012-02-28 11:30 ` Alex [this message]
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=loom.20120228T122833-822@post.gmane.org \
--to=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 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.