All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4 1/2] core: add tst_selinux_enabled() utility
Date: Wed, 23 Jul 2025 15:15:58 +0200	[thread overview]
Message-ID: <abbb4f90-d163-447a-bbb2-e860371e0179@suse.com> (raw)
In-Reply-To: <CAEjxPJ5g5EGQ-3Vq7b7YTnW6O0O=GM6yxxFa8cvfJ8uSjYTUTw@mail.gmail.com>


On 7/23/25 3:13 PM, Stephen Smalley wrote:
> To be more precise, the bug is only triggerable for LSMs that
> implement the listsecurity LSM hook (to return a synthesized security
> xattr regardless of whether one is set in the filesystem), which are
> only SELinux and Smack.

Thanks for the clarification. I guess we have a solution: we can take a 
look at /sys/kernel/security/lsm and verify if smack/selinux are enabled.

- Andrea


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-07-23 13:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22  6:55 [LTP] [PATCH v4 0/2] Add listxattr04 test reproducer Andrea Cervesato
2025-07-22  6:55 ` [LTP] [PATCH v4 1/2] core: add tst_selinux_enabled() utility Andrea Cervesato
2025-07-22 10:51   ` Petr Vorel
2025-07-22 12:06   ` Petr Vorel
2025-07-22 13:18     ` Stephen Smalley
2025-07-22 13:20       ` Stephen Smalley
2025-07-22 13:42         ` Petr Vorel
2025-07-22 13:48           ` Stephen Smalley
2025-07-23 11:17             ` Andrea Cervesato via ltp
2025-07-23 12:51               ` Petr Vorel
2025-07-23 11:19     ` Andrea Cervesato via ltp
2025-07-23 12:41       ` Petr Vorel
2025-07-23 12:43         ` Andrea Cervesato via ltp
2025-07-23 12:46           ` Stephen Smalley
2025-07-23 13:13             ` Stephen Smalley
2025-07-23 13:15               ` Andrea Cervesato via ltp [this message]
2025-07-23 19:50                 ` Petr Vorel
2025-07-22 19:12   ` Wei Gao via ltp
2025-07-22  6:55 ` [LTP] [PATCH v4 2/2] Add listxattr04 reproducer Andrea Cervesato
2025-07-22 14:11   ` Petr Vorel
2025-07-22 14:11     ` Petr Vorel

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=abbb4f90-d163-447a-bbb2-e860371e0179@suse.com \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.com \
    --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.