Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 19 Dec 2016 12:10:46 +0100
From: Emese Revfy <>
To: Kees Cook <>
Cc: ""
 <>, LKML <>,
 Arnd Bergmann <>, Josh Triplett <>, PaX
 Team <>, Brad Spengler <>, Michal
 Marek <>, Masahiro Yamada <>,
 linux-kbuild <>,, Russell
 King <>, Catalin Marinas <>,
 Rasmus Villemoes <>, David Brown
 <>, ""
 <>, Thomas Gleixner <>, Andrew
 Morton <>, Jeff Layton <>,
 Sam Ravnborg <>
Subject: Re: [PATCH v4 0/4] Introduce the initify gcc plugin

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.


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:// initify-v4


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.