All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Günther Noack" <gnoack@google.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>
Subject: Re: [PATCH] landlock_restrict_self.2: Fix max number of nested sandboxes
Date: Wed, 13 Mar 2024 10:07:52 +0100	[thread overview]
Message-ID: <ZfFs6Hw3endsIbzC@google.com> (raw)
In-Reply-To: <20240312151513.9718-1-mic@digikod.net>

On Tue, Mar 12, 2024 at 04:15:13PM +0100, Mickaël Salaün wrote:
> This limit was updated and backported with commit 75c542d6c6cc
> ("landlock: Reduce the maximum number of layers to 16") to all supported
> Linux versions.
> 
> Cc: Alejandro Colomar <alx@kernel.org>
> Cc: Günther Noack <gnoack@google.com>
> Signed-off-by: Mickaël Salaün <mic@digikod.net>
> ---
>  man2/landlock_restrict_self.2 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man2/landlock_restrict_self.2 b/man2/landlock_restrict_self.2
> index 43f15c932a83..fb7e48234098 100644
> --- a/man2/landlock_restrict_self.2
> +++ b/man2/landlock_restrict_self.2
> @@ -102,7 +102,7 @@ in its user namespace.
>  .TP
>  .B E2BIG
>  The maximum number of composed rulesets is reached for the calling thread.
> -This limit is currently 64.
> +This limit is currently 16.
>  .SH STANDARDS
>  Linux.
>  .SH HISTORY
> -- 
> 2.44.0
> 

Signed-off-by: Günther Noack <gnoack@google.com>

  reply	other threads:[~2024-03-13  9:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 15:15 [PATCH] landlock_restrict_self.2: Fix max number of nested sandboxes Mickaël Salaün
2024-03-13  9:07 ` Günther Noack [this message]
2024-03-13  9:12 ` Günther Noack
2024-03-14 16:08   ` Alejandro Colomar
2024-03-14 16:11     ` Alejandro Colomar
2024-03-14 16:49       ` Günther Noack
2024-03-14 17:12         ` Alejandro Colomar

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=ZfFs6Hw3endsIbzC@google.com \
    --to=gnoack@google.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mic@digikod.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 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.