From mboxrd@z Thu Jan 1 00:00:00 1970 Reply-To: kernel-hardening@lists.openwall.com Date: Wed, 11 Jan 2017 01:24:59 +0100 From: Emese Revfy Message-Id: <20170111012459.c0a0c615c99a389e4d89c8b5@gmail.com> In-Reply-To: References: <1481925984-98605-1-git-send-email-keescook@chromium.org> <20161219121046.646e5ef425178fce8c2cb555@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [kernel-hardening] Re: [PATCH v4 0/4] Introduce the initify gcc plugin To: Kees Cook Cc: "kernel-hardening@lists.openwall.com" , LKML , Arnd Bergmann , Josh Triplett , PaX Team , Brad Spengler , Michal Marek , Masahiro Yamada , linux-kbuild , minipli@ld-linux.so, Russell King , Catalin Marinas , Rasmus Villemoes , David Brown , "benh@kernel.crashing.org" , Thomas Gleixner , Andrew Morton , Jeff Layton , Sam Ravnborg List-ID: On Tue, 3 Jan 2017 16:23:03 -0800 Kees Cook wrote: > On Mon, Dec 19, 2016 at 3:10 AM, Emese Revfy wrote: > > On Fri, 16 Dec 2016 14:19:10 -0800 > > Kees Cook 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. Thanks for the report, you can find the fix here: https://github.com/ephox-gcc-plugins/initify/commit/5d93a54badd9751b79ef67ce8a8b4081fea37547 -- Emese