From: Stephen Smalley <sds@tycho.nsa.gov>
To: subodh.nijsure@gmail.com
Cc: linux-mtd@lists.infradead.org,
Artem Bityutskiy <dedekind1@gmail.com>,
casey@scahufler-ca.com, Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Subodh Nijsure <snijsure@grid-net.com>
Subject: Re: [PATCH v2] Add security.* XATTR support for the UBIFS
Date: Tue, 10 Apr 2012 08:46:25 -0400 [thread overview]
Message-ID: <1334061985.23411.3.camel@moss-pluto> (raw)
In-Reply-To: <1334015486-20616-1-git-send-email-snijsure@grid-net.com>
On Mon, 2012-04-09 at 16:51 -0700, subodh.nijsure@gmail.com wrote:
> From: Subodh Nijsure <snijsure@grid-net.com>
>
> Also fix couple of bugs in UBIFS extended attribute length calculation.
>
> Changes Since V1:
> Instead of just handling security.selinux extended attribute handle
> all security.* attributes.
>
> TESTING: Tested on MX28 based platforms using Micron MT29F2G08ABAEAH4 NAND
> With these change we are able to label UBIFS filesystem with
> security.selinux and run system with selinux enabled.
> This change also allows one to set other security.* extended
> attributesr, such as security.smack security.evm, security.ima
> Ran integck test on UBI filesystem.
>
> Signed-off-by: Subodh Nijsure <snijsure@grid-net.com>
> ---
> fs/ubifs/dir.c | 4 ++
> fs/ubifs/file.c | 6 ++
> fs/ubifs/journal.c | 12 +++-
> fs/ubifs/super.c | 3 +
> fs/ubifs/ubifs.h | 9 +++
> fs/ubifs/xattr.c | 147 ++++++++++++++++++++++++++++++++++++++++++++++++----
> 6 files changed, 167 insertions(+), 14 deletions(-)
>
> diff --git a/fs/ubifs/dir.c b/fs/ubifs/dir.c
> index ec9f187..f4e06c4 100644
> --- a/fs/ubifs/dir.c
> +++ b/fs/ubifs/dir.c
> @@ -293,6 +293,7 @@ static int ubifs_create(struct inode *dir, struct dentry *dentry, umode_t mode,
> ubifs_release_budget(c, &req);
> insert_inode_hash(inode);
> d_instantiate(dentry, inode);
> + ubifs_init_security(dir, inode, &dentry->d_name);
> return 0;
>
> out_cancel:
The ubifs_init_security() should occur before d_instantiate() so that
the inode is not accessible to other threads before its security
attributes have been set. And if it fails, you would ideally drop the
inode altogether and return an error to the creating process.
--
Stephen Smalley
National Security Agency
next prev parent reply other threads:[~2012-04-10 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 23:51 [PATCH v2] Add security.* XATTR support for the UBIFS subodh.nijsure
2012-04-10 12:46 ` Stephen Smalley [this message]
2012-04-11 13:00 ` Subodh Nijsure
2012-04-11 13:10 ` Stephen Smalley
2012-04-11 14:12 ` Subodh Nijsure
2012-04-11 14:23 ` Stephen Smalley
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=1334061985.23411.3.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=adrian.hunter@intel.com \
--cc=casey@scahufler-ca.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-security-module@vger.kernel.org \
--cc=snijsure@grid-net.com \
--cc=subodh.nijsure@gmail.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