linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Günther Noack" <gnoack3000@gmail.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH] samples/landlock: Document best-effort approach for LANDLOCK_ACCESS_FS_REFER
Date: Fri, 4 Nov 2022 18:01:49 +0100	[thread overview]
Message-ID: <Y2VFfdAdTY7b47D7@nuc> (raw)
In-Reply-To: <cbe72a75-b077-e5d2-52a8-db20432e15bc@digikod.net>

On Thu, Nov 03, 2022 at 03:21:32PM +0100, Mickaël Salaün wrote:
> On 30/10/2022 07:11, Günther Noack wrote:
> > Add a comment to clarify how to handle best-effort backwards
> > compatibility for LANDLOCK_ACCESS_FS_REFER.
> > 
> > The "refer" access is special because these operations are always
> > forbidden in ABI 1, unlike most other operations, which are permitted
> > when using Landlock ABI levels where they are not supported yet.
> > 
> > Signed-off-by: Günther Noack <gnoack3000@gmail.com>
> > ---
> >   samples/landlock/sandboxer.c | 16 +++++++++++++++-
> >   1 file changed, 15 insertions(+), 1 deletion(-)
> > 
> > diff --git a/samples/landlock/sandboxer.c b/samples/landlock/sandboxer.c
> > index fd4237c64fb2..901acb383124 100644
> > --- a/samples/landlock/sandboxer.c
> > +++ b/samples/landlock/sandboxer.c
> > @@ -234,7 +234,21 @@ int main(const int argc, char *const argv[], char *const *const envp)
> > +		 * If only ABI 1 is available, the sample tool knowingly forbids
> 
> s/the sample tool/this sandboxer/
> 
> > +		 * refer operations.
> > +		 *
> > +		 * If a program *needs* to do refer operations after enabling
> > +		 * Landlock, it can not use Landlock at ABI level 1.  To be
> > +		 * compatible across different kernels, such programs should
> > +		 * fall back to not using Landlock instead.
> 
> To be compatible with different kernel versions, such programs should then
> fall back to not restrict themselves at all if the running kernel only
> supports ABI 1.

Thanks for the review, Mickaël! Both suggestions applied, and sent V2.

—Günther

-- 

      reply	other threads:[~2022-11-04 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30  6:11 [PATCH] samples/landlock: Document best-effort approach for LANDLOCK_ACCESS_FS_REFER Günther Noack
2022-11-03 14:21 ` Mickaël Salaün
2022-11-04 17:01   ` Günther Noack [this message]

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=Y2VFfdAdTY7b47D7@nuc \
    --to=gnoack3000@gmail.com \
    --cc=linux-security-module@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;
as well as URLs for NNTP newsgroup(s).