[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHC9VhTH97P54tFYt92OU5058By2WMm12nMzTW+H_ofmnVRiDg@mail.gmail.com>
Date: Mon, 10 Feb 2025 09:51:52 -0500
From: Paul Moore <paul@...l-moore.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Hamza Mahfooz <hamzamahfooz@...ux.microsoft.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the security tree
On Sun, Feb 9, 2025 at 10:53 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> On Sun, 9 Feb 2025 22:44:42 -0500 Paul Moore <paul@...l-moore.com> wrote:
> >
> > On Sun, Feb 9, 2025 at 8:18 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > >
> > > After merging the security tree, today's linux-next build (arm
> > > multi_v7_defconfig) failed like this:
> > >
> > > In file included from include/linux/perf_event.h:62,
> > > from arch/arm/vfp/vfpmodule.c:21:
> > > include/linux/security.h:2379:12: warning: no previous prototype for 'security_uring_allowed' [-Wmissing-prototypes]
> > > 2379 | extern int security_uring_allowed(void)
> > > | ^~~~~~~~~~~~~~~~~~~~~~
> >
> > Thanks Stephen, I just pushed a fix to the LSM tree, it should be
> > fixed on your next pull.
> >
> > https://lore.kernel.org/linux-security-module/20250210034132.8448-2-paul@paul-moore.com/
>
> Shouldn't it be "static inline" instead of "extern inline"?
Yes it should :) Evidently I was fixated on the missing "inline" and
trying to fix it before bed that I missed the "extern" staring me
right in the face.
This will be fixed shortly.
--
paul-moore.com
Powered by blists - more mailing lists