public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org,
	"Mickaël Salaün" <mic@linux.microsoft.com>,
	"Mickaël Salaün" <mic@digikod.net>,
	"Günther Noack" <gnoack@google.com>,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH 1/1] landlock: Mention -1 return code on failure
Date: Fri, 12 Jul 2024 15:25:22 +0200	[thread overview]
Message-ID: <20240712132522.GB145191@pevik> (raw)
In-Reply-To: <evf3o7bjqr6262out6aazgbmmgm45o3gtuywdulrzhtd742p7n@v6xdj5yftinm>

> Hi Petr,

> On Fri, Jul 12, 2024 at 03:09:04PM GMT, Petr Vorel wrote:
> > Mention -1 return code on failure for landlock_add_rule(),
> > landlock_create_ruleset() and landlock_restrict_self().

> > Although it's a common rule to return -1 on error, it's better to be
> > explicit (as the other man pages are).

> > Fixes: a01d04a69 ("landlock_add_rule.2: Document new syscall")
> > Fixes: ca5163697 ("landlock_create_ruleset.2: Document new syscall")
> > Fixes: 3f7e4f808 ("landlock_restrict_self.2: Document new syscall")
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> > FYI we test return codes in LTP.

> > https://lore.kernel.org/ltp/20240711-landlock-v3-0-c7b0e9edf9b0@suse.com/
> > https://lore.kernel.org/ltp/20240711201306.98519-1-pvorel@suse.cz/

> > Kind regards,
> > Petr

> Thanks!  Please see a comment below.


> >  man/man2/landlock_add_rule.2       | 4 ++++
> >  man/man2/landlock_create_ruleset.2 | 4 ++++
> >  man/man2/landlock_restrict_self.2  | 4 ++++
> >  3 files changed, 12 insertions(+)

> > diff --git a/man/man2/landlock_add_rule.2 b/man/man2/landlock_add_rule.2
> > index 4b95afb07..6fdc2f896 100644
> > --- a/man/man2/landlock_add_rule.2
> > +++ b/man/man2/landlock_add_rule.2
> > @@ -79,6 +79,10 @@ must be 0.
> >  On success,
> >  .BR landlock_add_rule ()
> >  returns 0.
> > +On error,
> > +\-1 is returned and
> > +.I errno
> > +is set to indicate the cause of the error.
> >  .SH ERRORS
> >  .BR landlock_add_rule ()
> >  can fail for the following reasons:
> > diff --git a/man/man2/landlock_create_ruleset.2 b/man/man2/landlock_create_ruleset.2
> > index e62a3f9b9..4f638e85c 100644
> > --- a/man/man2/landlock_create_ruleset.2
> > +++ b/man/man2/landlock_create_ruleset.2
> > @@ -86,6 +86,10 @@ returns a new Landlock ruleset file descriptor,
> >  or a Landlock ABI version,
> >  according to
> >  .IR flags .
> > +On error,
> > +\-1 is returned and
> > +.I errno
> > +is set to indicate the cause of the error.

> I think the common wording is s/the cause of //

> Michael unified these a few years ago.

Yes, you're right, it's mentioned in Changes.old.
But I copied that from man/man2/mount_setattr.2 and it's on several places:

$ git grep "the cause of the error" man/ | wc -l
12

I'll send v2 later today or on Monday.

Kind regards,
Petr

> Cheers,
> Alex

> >  .SH ERRORS
> >  .BR landlock_create_ruleset ()
> >  can fail for the following reasons:
> > diff --git a/man/man2/landlock_restrict_self.2 b/man/man2/landlock_restrict_self.2
> > index 43f15c932..88850ddfb 100644
> > --- a/man/man2/landlock_restrict_self.2
> > +++ b/man/man2/landlock_restrict_self.2
> > @@ -72,6 +72,10 @@ must be 0.
> >  On success,
> >  .BR landlock_restrict_self ()
> >  returns 0.
> > +On error,
> > +\-1 is returned and
> > +.I errno
> > +is set to indicate the cause of the error.
> >  .SH ERRORS
> >  .BR landlock_restrict_self ()
> >  can fail for the following reasons:
> > -- 
> > 2.45.2

  reply	other threads:[~2024-07-12 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 13:09 [PATCH 1/1] landlock: Mention -1 return code on failure Petr Vorel
2024-07-12 13:13 ` Alejandro Colomar
2024-07-12 13:25   ` Petr Vorel [this message]
2024-07-12 13:26     ` Alejandro Colomar
2024-07-12 13:35 ` Günther Noack

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=20240712132522.GB145191@pevik \
    --to=pvorel@suse.cz \
    --cc=alx@kernel.org \
    --cc=gnoack@google.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=mic@linux.microsoft.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