From: Stephen Smalley <sds@tycho.nsa.gov>
To: Bhargava Shastry <bshas3@gmail.com>
Cc: SELinux@tycho.nsa.gov, Eric Paris <eparis@parisplace.org>,
James Morris <jmorris@namei.org>
Subject: Re: SELinux on Android
Date: Thu, 17 Nov 2011 08:37:14 -0500 [thread overview]
Message-ID: <1321537034.4836.8.camel@moss-pluto> (raw)
In-Reply-To: <CAGGozWR8pNNC6P1T8cYtbkfqZu56iVty+JdmXwudo3ZaAVbN-g@mail.gmail.com>
On Wed, 2011-11-16 at 19:15 +0100, Bhargava Shastry wrote:
> Hi again,
>
> I am trying to set/get file SELinux contexts using the set/getfilecon
> programs. I added debug prints in the kernel to track code flow. I
> notice that although setfilecon succeeds on a given file, a subsequent
> call to getfilecon on the same file returns the string "kernel"
> irrespective of the context that was set using setfilecon. On any
> other file whose context is not set yet, getfilecon properly returns
> the string "unlabeled"
>
> I suspect the inode struct in the kernel is not being updated properly
> after a setxattr call. Has anyone else faced a similar problem? I am
> working on Android's Nexus one phone.
- Do you have a policy loaded (requires patching init to load the
policy)?
- Do you have yaffs xattr support enabled in your kernel
(CONFIG_YAFFS_XATTR=y)?
- Do you have the two patches for yaffs that I posted (one of which they
did take, the other they ignored)?
http://www.aleph1.co.uk/lurker/message/20110412.193746.891b5e18.en.html
http://www.aleph1.co.uk/lurker/message/20110413.203654.65d7ee58.en.html
--
Stephen Smalley
National Security Agency
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2011-11-17 13:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 10:16 SELinux on Android Bhargava Shastry
2011-11-04 10:54 ` Russell Coker
2011-11-04 12:32 ` Stephen Smalley
2011-11-04 16:25 ` Bhargava Shastry
2011-11-04 16:59 ` Stephen Smalley
2011-11-10 10:33 ` Bhargava Shastry
2011-11-10 12:48 ` Russell Coker
2011-11-10 13:11 ` Eric Paris
2011-11-10 13:12 ` Stephen Smalley
2011-11-10 13:26 ` Bhargava Shastry
2011-11-10 16:26 ` Stephen Smalley
2011-11-11 11:33 ` Bhargava Shastry
2011-11-16 18:15 ` Bhargava Shastry
2011-11-16 18:35 ` Eric Paris
2011-11-17 10:15 ` Bhargava Shastry
2011-11-17 13:39 ` Stephen Smalley
2011-11-21 15:45 ` Bhargava Shastry
2011-11-21 15:51 ` Stephen Smalley
2011-11-21 18:18 ` Bhargava Shastry
2011-11-21 18:32 ` Stephen Smalley
2011-11-22 19:25 ` Bhargava Shastry
2011-11-22 19:29 ` Stephen Smalley
2011-11-22 22:03 ` Russell Coker
2011-12-01 18:42 ` Bhargava Shastry
2011-12-01 19:04 ` Stephen Smalley
2011-12-02 10:37 ` Bhargava Shastry
2011-11-17 13:37 ` Stephen Smalley [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=1321537034.4836.8.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=SELinux@tycho.nsa.gov \
--cc=bshas3@gmail.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.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.