public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Günther Noack" <gnoack@google.com>
Cc: "Mickaël Salaün" <mic@digikod.net>, linux-man@vger.kernel.org
Subject: Re: [PATCH] landlock_restrict_self.2: Fix max number of nested sandboxes
Date: Thu, 14 Mar 2024 17:11:00 +0100	[thread overview]
Message-ID: <ZfMhlJ59U3WfG-d6@debian> (raw)
In-Reply-To: <ZfMg4rZRbjSP4mFn@debian>

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

Hi Günther, Mickaël,

On Thu, Mar 14, 2024 at 05:08:02PM +0100, Alejandro Colomar wrote:
> > >  .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.

BTW, do you think this limit change is something relevant for HISTORY?
Or should we maybe not document the limit?  Or maybe should the kernel
provide a macro to name that limit (and thus let a user grep it in their
headers to learn their specific value)?  Or maybe a combination?

Cheers,
Alex


-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-03-14 16:11 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
2024-03-13  9:12 ` Günther Noack
2024-03-14 16:08   ` Alejandro Colomar
2024-03-14 16:11     ` Alejandro Colomar [this message]
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=ZfMhlJ59U3WfG-d6@debian \
    --to=alx@kernel.org \
    --cc=gnoack@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox