From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: Paul Moore <paul@paul-moore.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, revest@chromium.org,
jackmanb@chromium.org, jmorris@namei.org, serge@hallyn.com,
bpf@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [RFC][PATCH 2/4] lsm: Add missing return values doc in lsm_hooks.h and fix formatting
Date: Wed, 16 Nov 2022 09:06:55 +0100 [thread overview]
Message-ID: <dd9215b603d9ff511c5c23998b4597b0eb55f0a7.camel@huaweicloud.com> (raw)
In-Reply-To: <CAHC9VhQjtU0DFoVGav-nBh-09QXh+X=Cf8RgJz6nAjvcyNQ-5A@mail.gmail.com>
On Tue, 2022-11-15 at 21:23 -0500, Paul Moore wrote:
> On Tue, Nov 15, 2022 at 12:57 PM Roberto Sassu
> <roberto.sassu@huaweicloud.com> wrote:
> > From: Roberto Sassu <roberto.sassu@huawei.com>
> >
> > Ensure that for non-void LSM hooks there is a description of the return
> > values. Also replace spaces with tab for indentation, remove empty lines
> > between the hook description and the list of parameters and add the period
> > at the end of the parameter description.
> >
> > Finally, replace the description of the sb_parse_opts_str hook, which was
> > removed with commit 757cbe597fe8 ("LSM: new method: ->sb_add_mnt_opt()"),
> > with one for the new hook sb_add_mnt_opt.
> >
> > Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
> > ---
> > include/linux/lsm_hooks.h | 123 ++++++++++++++++++++++++++------------
> > 1 file changed, 86 insertions(+), 37 deletions(-)
>
> ...
>
> > diff --git a/include/linux/lsm_hooks.h b/include/linux/lsm_hooks.h
> > index f40b82ca91e7..c0c570b7eabd 100644
> > --- a/include/linux/lsm_hooks.h
> > +++ b/include/linux/lsm_hooks.h
> > @@ -176,18 +183,22 @@
> > * Set the security relevant mount options used for a superblock
> > * @sb the superblock to set security mount options for
> > * @opts binary data structure containing all lsm mount data
> > + * Return 0 on success, error on failure.
> > * @sb_clone_mnt_opts:
> > * Copy all security options from a given superblock to another
> > * @oldsb old superblock which contain information to clone
> > * @newsb new superblock which needs filled in
> > - * @sb_parse_opts_str:
> > - * Parse a string of security data filling in the opts structure
> > - * @options string containing all mount options known by the LSM
> > - * @opts binary data structure usable by the LSM
> > + * Return 0 on success, error on failure.
> > + * @add_mnt_opt:
> > + * Add a new mount option @option with value @val and length @len to the
> > + * existing mount options @mnt_opts.
> > + * Return 0 if the option was successfully added, a negative value
> > + * otherwise.
>
> I really appreciate the effort to improve the LSM hook comments/docs,
> but the "sb_add_mnt_opt" hook was removed in 52f982f00b22
> ("security,selinux: remove security_add_mnt_opt()").
Right, sorry, didn't notice.
Thanks
Roberto
next prev parent reply other threads:[~2022-11-16 8:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 17:56 [RFC][PATCH 0/4] security: Ensure LSMs return expected values Roberto Sassu
2022-11-15 17:56 ` [RFC][PATCH 1/4] lsm: Clarify documentation of vm_enough_memory hook Roberto Sassu
2022-11-16 2:11 ` Paul Moore
2022-11-16 8:06 ` Roberto Sassu
2022-11-16 19:17 ` KP Singh
2022-11-16 19:27 ` Paul Moore
2022-11-15 17:56 ` [RFC][PATCH 2/4] lsm: Add missing return values doc in lsm_hooks.h and fix formatting Roberto Sassu
2022-11-16 2:23 ` Paul Moore
2022-11-16 8:06 ` Roberto Sassu [this message]
2022-11-16 19:26 ` Paul Moore
2022-11-15 17:56 ` [RFC][PATCH 3/4] lsm: Redefine LSM_HOOK() macro to add return value flags as argument Roberto Sassu
2022-11-16 2:27 ` Paul Moore
2022-11-16 8:11 ` Roberto Sassu
2022-11-16 22:04 ` Paul Moore
2022-11-17 5:49 ` Greg KH
2022-11-17 15:31 ` Paul Moore
2022-11-15 17:56 ` [RFC][PATCH 4/4] security: Enforce limitations on return values from LSMs Roberto Sassu
2022-11-16 2:35 ` Paul Moore
2022-11-16 14:36 ` Roberto Sassu
2022-11-16 15:47 ` [PoC][PATCH] bpf: Call return value check function in the JITed code Roberto Sassu
2022-11-16 16:16 ` Alexei Starovoitov
2022-11-16 16:41 ` Roberto Sassu
2022-11-16 17:55 ` Alexei Starovoitov
2022-11-16 18:29 ` Casey Schaufler
2022-11-16 19:04 ` KP Singh
2022-11-16 22:40 ` Paul Moore
2022-11-30 13:52 ` Roberto Sassu
2022-11-16 17:12 ` Casey Schaufler
2022-11-16 19:02 ` KP Singh
2022-11-18 8:44 ` Roberto Sassu
2022-11-21 15:31 ` Roberto Sassu
2022-11-16 22:06 ` [RFC][PATCH 4/4] security: Enforce limitations on return values from LSMs Paul Moore
2022-11-15 18:41 ` [RFC][PATCH 0/4] security: Ensure LSMs return expected values Casey Schaufler
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=dd9215b603d9ff511c5c23998b4597b0eb55f0a7.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=jackmanb@chromium.org \
--cc=jmorris@namei.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=paul@paul-moore.com \
--cc=revest@chromium.org \
--cc=roberto.sassu@huawei.com \
--cc=sdf@google.com \
--cc=serge@hallyn.com \
--cc=song@kernel.org \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).