public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ben Shelton <ben.shelton@ni.com>
Cc: linux-mtd@lists.infradead.org, adrian.hunter@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] UBIFS: add xattr support for security / SELinux
Date: Fri, 07 Nov 2014 11:53:50 +0200	[thread overview]
Message-ID: <1415354030.958.304.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1414781431-2911-1-git-send-email-ben.shelton@ni.com>

On Fri, 2014-10-31 at 13:50 -0500, Ben Shelton wrote:
> I'm reposting the patch series for security xattr / SELinux support on UBIFS
> from Subodh Nijsure and Marc Kleine-Budde [1] in order to restart the process
> of getting this support upstream.
> 
> Notes:
> 
>  - I removed 'UBIFS: xattr: protect ui_size and data_len by ui_mutex' because
>    after looking through the comments before the definition of struct
>    ubifs_inode, I'm not sure what this was intended to fix.  It looks like
>    i_size and data_len are not intended to be protected by ui_mutex, and I'm
>    unclear on why ui->ui_size needs to be protected here by host_ui's ui_mutex.
>    CCing Marc -- could you comment on how this is supposed to work?

Thanks, I'll be looking at this as time allows. I think the MTD web site
mentioned somewhere that SELinux is not supported or something. In any
case, once we support SELinux, we need to tell on the web site that we
support it.

Which reminds me that I need to update the web-site and tell there that
I do not support the backport trees any longer...

      parent reply	other threads:[~2014-11-07  9:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 18:50 [PATCH 0/4] UBIFS: add xattr support for security / SELinux Ben Shelton
2014-10-31 18:50 ` [PATCH 1/4] UBIFS: fix a couple bugs in UBIFS xattr length calculation Ben Shelton
2014-11-07 10:34   ` Artem Bityutskiy
2014-11-07 19:56     ` Ben Shelton
2014-10-31 18:50 ` [PATCH 2/4] UBIFS: Add xattr support for symlinks Ben Shelton
2014-11-10 14:01   ` Artem Bityutskiy
2014-11-10 17:12     ` Ben Shelton
2014-11-11 10:17       ` Artem Bityutskiy
2014-11-11 11:04   ` Artem Bityutskiy
2014-10-31 18:50 ` [PATCH 3/4] UBIFS: Add security.* XATTR support for the UBIFS Ben Shelton
2014-11-11 11:07   ` Artem Bityutskiy
2014-10-31 18:50 ` [PATCH 4/4] UBIFS: add ubifs_err() to print error reason Ben Shelton
2014-11-11 11:10   ` Artem Bityutskiy
2014-11-11 16:08     ` Ben Shelton
2014-11-12 12:31       ` Artem Bityutskiy
2014-11-07  9:53 ` Artem Bityutskiy [this message]

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=1415354030.958.304.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=ben.shelton@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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