[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190730082618.5bb5edf3@canb.auug.org.au>
Date: Tue, 30 Jul 2019 08:26:18 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Denis Efremov <efremov@...ux.com>
Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michal Marek <michal.lkml@...kovi.net>,
Emil Velikov <emil.l.velikov@...il.com>,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] modpost: check for static EXPORT_SYMBOL* functions
Hi Denis,
On Mon, 29 Jul 2019 17:18:01 +0300 Denis Efremov <efremov@...ux.com> wrote:
>
> This patch adds a check to warn about static EXPORT_SYMBOL* functions
> during the modpost. In most of the cases, a static symbol marked for
> exporting is an odd combination that should be fixed either by deleting
> the exporting mark or by removing the static attribute and adding the
> appropriate declaration to headers.
OK, this is now in linux-next and I am getting what look like false
positives :-(
My powerpc builds produce these:
WARNING: "ahci_em_messages" [vmlinux] is the static EXPORT_SYMBOL_GPL
WARNING: "ftrace_set_clr_event" [vmlinux] is the static EXPORT_SYMBOL_GPL
WARNING: "empty_zero_page" [vmlinux] is the static EXPORT_SYMBOL
WARNING: "jiffies" [vmlinux] is the static EXPORT_SYMBOL
empty_zero_page (at least) is not static. It is defined in assembler ...
jiffies is defined in arch/powerpc/kernel/vmlinux.lds.S as an alias for
(part of) jiffies_64 which is not static (defined in kernel/time/timer.c).
The other 2 were OK.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists