From: Paul Moore <paul@paul-moore.com>
To: linux-security-module@vger.kernel.org
Cc: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
Subject: Re: [PATCH] lsm: fix a missing security_uring_allowed() prototype
Date: Mon, 10 Feb 2025 09:56:36 -0500 [thread overview]
Message-ID: <CAHC9VhQfiABZQagVsZV81NyW2Gm8htwHjG7EHiUTt_LSebDUTA@mail.gmail.com> (raw)
In-Reply-To: <20250210034132.8448-2-paul@paul-moore.com>
On Sun, Feb 9, 2025 at 10:41 PM Paul Moore <paul@paul-moore.com> wrote:
>
> The !CONFIG_SECURITY dummy function was missing an inline attribute which
> caused the compiler to complain about a missing prototype. This patch
> adds the missing inline attribute.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/oe-kbuild-all/202502081912.TeokpAAe-lkp@intel.com/
> Fixes: c6ad9fdbd44b ("io_uring,lsm,selinux: add LSM hooks for io_uring_setup()")
> Signed-off-by: Paul Moore <paul@paul-moore.com>
> ---
> include/linux/security.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/security.h b/include/linux/security.h
> index 3e68f8468a22..fab843d5e621 100644
> --- a/include/linux/security.h
> +++ b/include/linux/security.h
> @@ -2376,7 +2376,7 @@ static inline int security_uring_cmd(struct io_uring_cmd *ioucmd)
> {
> return 0;
> }
> -extern int security_uring_allowed(void)
> +extern inline int security_uring_allowed(void)
The extern also needed to be changed out, essentially doing s/extern
int/static inline/. Regardless, this is now merged into lsm/dev.
> {
> return 0;
> }
> --
> 2.48.1
--
paul-moore.com
prev parent reply other threads:[~2025-02-10 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 3:41 [PATCH] lsm: fix a missing security_uring_allowed() prototype Paul Moore
2025-02-10 14:56 ` Paul Moore [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=CAHC9VhQfiABZQagVsZV81NyW2Gm8htwHjG7EHiUTt_LSebDUTA@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=hamzamahfooz@linux.microsoft.com \
--cc=linux-security-module@vger.kernel.org \
/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).