mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fan Wu <wufan@kernel.org>
To: corbet@lwn.net, jmorris@namei.org, paul@paul-moore.com, serge@hallyn.com
Cc: linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] ipe: add 'anonymous_memory' property for policy decisions
Date: Thu, 24 Oct 2024 15:13:27 -0700	[thread overview]
Message-ID: <8ee41bc4-ca8e-416f-8219-12d4a83e5f8b@kernel.org> (raw)
In-Reply-To: <1728582157-13884-1-git-send-email-wufan@linux.microsoft.com>

Since this patch is quite straightforward, I have merged it into the ipe#next branch for testing and will send it to Linus during the next merge window.


-Fan

On 2024/10/10 10:42, Fan Wu wrote:
> Currently, all existing IPE properties evaluate to FALSE for
> operations triggered by anonymous memory regions. As a result,
> IPE falls back to the policy's default action for such operations.
>
> In policies where the default action is DENY, this behavior blocks
> all anonymous memory operations, rendering binaries that rely on
> anonymous memory unusable.
>
> This commit introduces a new IPE property, 'anonymous_memory',
> which evaluates to TRUE when an operation is triggered by an
> anonymous memory region. This allows administrators to explicitly
> allow or deny operations involving anonymous memory.
>
> Signed-off-by: Fan Wu <wufan@linux.microsoft.com>
> ---
>  Documentation/admin-guide/LSM/ipe.rst | 11 +++++++++++
>  Documentation/security/ipe.rst        |  9 +++++----
>  security/ipe/Kconfig                  | 10 ++++++++++
>  security/ipe/audit.c                  |  2 ++
>  security/ipe/eval.c                   | 26 ++++++++++++++++++++++++++
>  security/ipe/policy.h                 |  2 ++
>  security/ipe/policy_parser.c          |  4 ++++
>  7 files changed, 60 insertions(+), 4 deletions(-)

  reply	other threads:[~2024-10-24 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 17:42 Fan Wu
2024-10-24 22:13 ` Fan Wu [this message]
2024-10-25 22:32   ` Fan Wu

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=8ee41bc4-ca8e-416f-8219-12d4a83e5f8b@kernel.org \
    --to=wufan@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jmorris@namei.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®