From: Artem Bityutskiy <dedekind1@gmail.com>
To: Steve Iribarne <siribarne@grid-net.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: xattr question AGAIN!
Date: Fri, 25 Feb 2011 10:58:59 +0200 [thread overview]
Message-ID: <1298624339.2798.18.camel@localhost> (raw)
In-Reply-To: <4D5C200C.3010007@grid-net.com>
On Wed, 2011-02-16 at 11:05 -0800, Steve Iribarne wrote:
> Sorry for the repeat but I just want to be sure I'm getting this right.
>
> So the UBIFS supports most of the SELinux xattrs. I believe the only
> exception is ACL.
>
> Is this a correct assumption?
Yes. However, we never tried selinux, so there may be some issues. We
might forget to do some small thing.
> And we are going to start doing some extensive testing on this, so I'll
> report any issues we find. I also may have resources to add ACL support.
Just try if selinux xattrs are supported or not and report back please.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-02-25 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 19:05 xattr question AGAIN! Steve Iribarne
2011-02-25 8:58 ` 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=1298624339.2798.18.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=siribarne@grid-net.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