linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Dorfman <kdorfman@codeaurora.org>
To: jaegeuk.kim@samsung.com,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: f2fs xattr and SELinux
Date: Mon, 02 Dec 2013 17:00:30 +0200	[thread overview]
Message-ID: <529CA08E.5010206@codeaurora.org> (raw)
In-Reply-To: <29495453.293471385942943622.JavaMail.weblogic@epv6ml06>

Hello Jaegeuk,

What is seclabel config of F2FS partition?
I do not see seclabel mount option for /data partition (f2fs type), 
while there is such option for ext4.

Thanks,
Kostya


On 12/02/2013 02:09 AM, Jaegeuk Kim wrote:
> Hi,
>
> Could you check the config of F2FS?
> There should be a seclabel config.
> Thanks,
>
>
> ------- Original Message -------
> Sender : Konstantin Dorfman<kdorfman@codeaurora.org>
> Date : 2013-12-02 02:09 (GMT+09:00)
> Title : f2fs xattr and SELinux
>
> Hi all,
>
> I'm trying to use f2fs xattr with SELinux (on android) and getting
> following error:
>
> root# restorecon -Rv /data
> Relabeling /data from u:object_r:unlabeled:s0 to
> u:object_r:system_data_file:s0.
> Could not label /data with u:object_r:system_data_file:s0: Operation not
> supported on transport endpoint
>
> Also, output of `ls -Z` command (all files/dirs are unlabeled):
>
> root# ls -Z /data
> drwxrwx--x system   system            u:object_r:unlabeled:s0 app
> drwxr-x--x root     root              u:object_r:unlabeled:s0 app_tests
> drwxr-x--x root     root              u:object_r:unlabeled:s0 audio-encode
> drwxr-x--x root     root              u:object_r:unlabeled:s0 busybox
> drwxrwx--x system   system            u:object_r:unlabeled:s0 connectivity
> drwxr-x--x root     root              u:object_r:unlabeled:s0 data_test
> drwxr-x--x root     root              u:object_r:unlabeled:s0 evt-test
> drwxr-x--x root     root              u:object_r:unlabeled:s0 fstest
> drwxr-x--x root     root              u:object_r:unlabeled:s0 gps-test
> drwxr-x--x root     root              u:object_r:unlabeled:s0 graphics_tests
> drwxr-x--x root     root              u:object_r:unlabeled:s0
> instrumentation_tests
> drwxr-x--x root     root              u:object_r:unlabeled:s0 kernel-tests
> drwxrwx--- root     root              u:object_r:unlabeled:s0 lost+found
> drwxrwx--- media_rw media_rw          u:object_r:unlabeled:s0 media
>
> mount output is:
> /dev/block/bootdevice/by-name/userdata /data f2fs
> rw,nosuid,nodev,relatime,background_gc_on,discard,user_xattr,acl,active_logs=6
> 0 0
>
> Any comments/ideas about why xattr is not working for me on f2fs?
>
> Thanks,
> Kostya
>


-- 
sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation


  reply	other threads:[~2013-12-02 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02  0:09 f2fs xattr and SELinux Jaegeuk Kim
2013-12-02 15:00 ` Konstantin Dorfman [this message]
2013-12-03 16:31 ` Konstantin Dorfman
2013-12-04  8:02   ` Jaegeuk Kim
  -- strict thread matches above, loose matches on Subject: below --
2013-12-01 17:09 Konstantin Dorfman

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=529CA08E.5010206@codeaurora.org \
    --to=kdorfman@codeaurora.org \
    --cc=jaegeuk.kim@samsung.com \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).