[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 19 Dec 2016 12:10:46 +0100
From: Emese Revfy <re.emese@...il.com>
To: Kees Cook <keescook@...omium.org>
Cc: "kernel-hardening@...ts.openwall.com"
<kernel-hardening@...ts.openwall.com>, LKML <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>, Josh Triplett <josh@...htriplett.org>, PaX
Team <pageexec@...email.hu>, Brad Spengler <spender@...ecurity.net>, Michal
Marek <mmarek@...e.com>, Masahiro Yamada <yamada.masahiro@...ionext.com>,
linux-kbuild <linux-kbuild@...r.kernel.org>, minipli@...linux.so, Russell
King <linux@...linux.org.uk>, Catalin Marinas <catalin.marinas@....com>,
Rasmus Villemoes <linux@...musvillemoes.dk>, David Brown
<david.brown@...aro.org>, "benh@...nel.crashing.org"
<benh@...nel.crashing.org>, Thomas Gleixner <tglx@...utronix.de>, Andrew
Morton <akpm@...ux-foundation.org>, Jeff Layton <jlayton@...chiereds.net>,
Sam Ravnborg <sam@...nborg.org>
Subject: Re: [PATCH v4 0/4] Introduce the initify gcc plugin
On Fri, 16 Dec 2016 14:19:10 -0800
Kees Cook <keescook@...omium.org> wrote:
> FWIW, it still seems to me that these aren't false positives:
>
> WARNING: vmlinux.o(.text.unlikely+0x1b1): Section mismatch in
> reference from the function uncore_pci_exit.part.22() to the function
> .init.text:uncore_free_pcibus_map()
> The function uncore_pci_exit.part.22() references
> the function __init uncore_free_pcibus_map().
> This is often because uncore_pci_exit.part.22 lacks a __init
> annotation or the annotation of uncore_free_pcibus_map is wrong.
Hi,
I can't reproduce this section mismatch. Could you please send me your .config?
Which gcc version did you use?
I used this tree: git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git initify-v4
Thanks
--
Emese
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
