Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] fs/cramfs: add depends on !BR2_PACKAGE_LIBSELINUX
Date: Sat, 14 Mar 2020 15:36:10 +0100	[thread overview]
Message-ID: <20200314153610.582f6fe9@windsurf> (raw)
In-Reply-To: <20200312182941.3322627-1-aduskett@gmail.com>

Hello,

On Thu, 12 Mar 2020 11:29:38 -0700
aduskett at gmail.com wrote:

> From: Adam Duskett <Aduskett@gmail.com>
> 
> cramfs does not support extended attributes (xattrs) needed for SELinux to
> function.
> 
> Signed-off-by: Adam Duskett <Aduskett@gmail.com>

I quickly discussed this with Peter on IRC, and we both agreed we
didn't like these direct dependencies.

One solution I suggested is to do something like this:

 - Introduce some hidden boolean like BR2_SYSTEM_NEEDS_XATTR_FS (or
   some better name)

 - Have libselinux select this

 - Have the filesystems that don't support xattr have a depends on
   !BR2_SYSTEM_NEEDS_XATTR_FS.

I'm just not sure about where to define BR2_SYSTEM_NEEDS_XATTR_FS, and
I'm not sure about the naming. Should it be in fs/Config.in? In
system/Config.in?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2020-03-14 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 18:29 [Buildroot] [PATCH 1/3] fs/cramfs: add depends on !BR2_PACKAGE_LIBSELINUX aduskett at gmail.com
2020-03-12 18:29 ` [Buildroot] [PATCH 2/3] fs/romfs: " aduskett at gmail.com
2020-03-12 18:29 ` [Buildroot] [PATCH 3/3] fss/yaffs2: " aduskett at gmail.com
2020-03-14 14:36 ` Thomas Petazzoni [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=20200314153610.582f6fe9@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.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