From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: ext akshay st <akshayts@yahoo.co.in>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS and mkfs.ubifs Security Extended attribute support patch available?
Date: Fri, 04 Jun 2010 08:15:00 +0300 [thread overview]
Message-ID: <1275628500.25847.4.camel@localhost> (raw)
In-Reply-To: <934572.90077.qm@web94913.mail.in2.yahoo.com>
On Thu, 2010-06-03 at 17:32 +0200, ext akshay st wrote:
> Hi Artem
> I understand now that it is not completely supported,I also
> wanted to know is there anything to be done in mkfs.ubifs
> for security xattr.
I do not know, you need to look at the sources and try.
> I feel I can just add
> securityinitinode() while creating a new inode in Linux
> kernel?
Probably, I do not have time to look at this now, but if you submit me
tested patches, I'll happily accept them.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next parent reply other threads:[~2010-06-04 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <934572.90077.qm@web94913.mail.in2.yahoo.com>
2010-06-04 5:15 ` Artem Bityutskiy [this message]
2010-06-03 8:08 UBIFS and mkfs.ubifs Security Extended attribute support patch available? akshay st
2010-06-03 14:28 ` Artem Bityutskiy
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=1275628500.25847.4.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=akshayts@yahoo.co.in \
--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