From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH] mkfs.f2fs: avoid selinux denial for unnecessary sysfs node
Date: Mon, 30 Apr 2018 19:44:27 -0700 [thread overview]
Message-ID: <20180501024427.24114-1-jaegeuk@kernel.org> (raw)
This avoids unnecessary sysfs node access causing selinux denial.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
lib/libf2fs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/libf2fs.c b/lib/libf2fs.c
index 05b026b..69cf98b 100644
--- a/lib/libf2fs.c
+++ b/lib/libf2fs.c
@@ -533,7 +533,7 @@ __u32 f2fs_inode_chksum(struct f2fs_node *node)
*/
const char *get_rootdev()
{
-#ifdef ANDROID_WINDOWS_HOST
+#if defined(ANDROID_WINDOWS_HOST) || defined(WITH_ANDROID)
return NULL;
#else
struct stat sb;
--
2.17.0.484.g0c8726318c-goog
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next reply other threads:[~2018-05-01 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 2:44 Jaegeuk Kim [this message]
2018-05-04 10:06 ` [PATCH] mkfs.f2fs: avoid selinux denial for unnecessary sysfs node Chao Yu
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=20180501024427.24114-1-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).