From: Ritesh Harjani <riteshh@codeaurora.org>
To: linux-mtd@lists.infradead.org, richard@nod.at,
david.oberhollenzer@sigma-star.at
Cc: Ritesh Harjani <riteshh@codeaurora.org>
Subject: [RFC PATCH 0/2] mkfs.ubifs: Implement selinux labelling support
Date: Wed, 6 Jun 2018 15:08:58 +0530 [thread overview]
Message-ID: <1528277940-30919-1-git-send-email-riteshh@codeaurora.org> (raw)
Hi All,
This patchset implements the selinux context labelling support
in mkfs.ubifs utility which was discussed here [1].
Patchset is based upon previous work done by John [2].
Commit texts should explain about the change description.
I have tested this on my 4.9 kernel NAND based internal device with
UBIFS and selinux enabled. With this we are able to set the
respective selinux labels based on the input file_context provided
in mkfs.ubifs command.
[1]:- http://lists.infradead.org/pipermail/linux-mtd/2018-May/081138.html
[2]:- http://lists.infradead.org/pipermail/linux-mtd/2014-February/052136.html
Ritesh Harjani (2):
mkfs.ubifs: add_xattr is not depending on host XATTR support
mkfs.ubifs: Implement selinux labelling support in mkfs.ubifs.
Makefile.am | 4 +
configure.ac | 27 +++++
ubifs-utils/Makemodule.am | 4 +-
ubifs-utils/mkfs.ubifs/mkfs.ubifs.c | 197 ++++++++++++++++++++++++++++--------
4 files changed, 189 insertions(+), 43 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
next reply other threads:[~2018-06-06 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 9:38 Ritesh Harjani [this message]
2018-06-06 9:38 ` [RFC PATCH 1/2] mkfs.ubifs: add_xattr is not depending on host XATTR support Ritesh Harjani
2018-06-06 9:39 ` [RFC PATCH 2/2] mkfs.ubifs: Implement selinux labelling support in mkfs.ubifs Ritesh Harjani
2018-06-11 4:27 ` [RFC PATCH 0/2] mkfs.ubifs: Implement selinux labelling support Ritesh Harjani
2018-06-11 7:00 ` Richard Weinberger
2018-06-11 11:23 ` Ritesh Harjani
2018-06-14 7:33 ` David Oberhollenzer
2018-06-14 11:31 ` Ritesh Harjani
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=1528277940-30919-1-git-send-email-riteshh@codeaurora.org \
--to=riteshh@codeaurora.org \
--cc=david.oberhollenzer@sigma-star.at \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).