All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rahul Sandhu" <nvraxn@gmail.com>
To: <paul@paul-moore.com>
Cc: <omosnace@redhat.com>, <selinux@vger.kernel.org>,
	<stephen.smalley.work@gmail.com>
Subject: Re: ls from coreutils 9.6 doesn't show labels of some files
Date: Tue, 22 Apr 2025 17:31:21 +0100	[thread overview]
Message-ID: <D9DB7KSD01JE.1LSPBCYV65C6Y@gmail.com> (raw)
In-Reply-To: <CAHC9VhRj4CWBbSCEiznjNh_WaHr2vEGB-_Xem=VqRyptR=MtGw@mail.gmail.com>

Hey,

> I can't think of a good reason why we would ever want the *listxattr()
> syscalls to not provide security.selinux, if there is an individual
> filesystem that is different/broken in this regard it should be
> treated as a BUG and fixed.

I've spoken to coreutils upstream[1], and they also seem to see this as
something which should be fixed in the kernel too[2][3], and appear to
want a soloution in the kernel rather than working around it in ls(1).

Thanks,
Rahul

[1] https://lists.gnu.org/archive/html/bug-coreutils/2025-04/msg00011.html
[2] https://lists.gnu.org/archive/html/bug-coreutils/2025-04/msg00025.html
[3] https://lists.gnu.org/archive/html/bug-coreutils/2025-04/msg00031.html

  reply	other threads:[~2025-04-22 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 15:11 ls from coreutils 9.6 doesn't show labels of some files Ondrej Mosnacek
2025-01-28 15:26 ` Stephen Smalley
2025-01-28 16:08   ` Paul Moore
2025-04-22 16:31     ` Rahul Sandhu [this message]
2025-04-22 17:28       ` Stephen Smalley
2025-04-22 17:35         ` Dominick Grift
2025-04-22 18:06       ` Casey Schaufler
2025-04-22 18:57         ` Stephen Smalley

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=D9DB7KSD01JE.1LSPBCYV65C6Y@gmail.com \
    --to=nvraxn@gmail.com \
    --cc=omosnace@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@gmail.com \
    /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.