Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-02-20 Thread Emese Revfy
On Wed, 15 Feb 2017 11:27:06 -0800 Kees Cook wrote: > On Tue, Feb 14, 2017 at 4:23 PM, Emese Revfy wrote: > > On Thu, 12 Jan 2017 15:40:41 -0800 > > Kees Cook wrote: > > > >> WARNING: drivers/clk/bcm/built-in.o(.text+0xec2): Section mismatch in > >> reference from the function clk_gate() to the

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-02-15 Thread Kees Cook
On Tue, Feb 14, 2017 at 4:23 PM, Emese Revfy wrote: > On Thu, 12 Jan 2017 15:40:41 -0800 > Kees Cook wrote: > >> WARNING: drivers/clk/bcm/built-in.o(.text+0xec2): Section mismatch in >> reference from the function clk_gate() to the variable >> .init.rodata.str:__func__.29708 >> The function clk_g

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-02-14 Thread Emese Revfy
On Thu, 12 Jan 2017 15:40:41 -0800 Kees Cook wrote: > WARNING: drivers/clk/bcm/built-in.o(.text+0xec2): Section mismatch in > reference from the function clk_gate() to the variable > .init.rodata.str:__func__.29708 > The function clk_gate() references > the variable __initconst __func__.29708. >

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-01-18 Thread Kees Cook
On Tue, Jan 17, 2017 at 12:31 PM, Emese Revfy wrote: > On Thu, 12 Jan 2017 15:40:41 -0800 > Kees Cook wrote: > >> WARNING: drivers/clk/bcm/built-in.o(.text+0xec2): Section mismatch in >> reference from the function clk_gate() to the variable >> .init.rodata.str:__func__.29708 >> The function clk_

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-01-17 Thread Emese Revfy
On Thu, 12 Jan 2017 15:40:41 -0800 Kees Cook wrote: > WARNING: drivers/clk/bcm/built-in.o(.text+0xec2): Section mismatch in > reference from the function clk_gate() to the variable > .init.rodata.str:__func__.29708 > The function clk_gate() references > the variable __initconst __func__.29708. >

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-01-12 Thread Kees Cook
On Thu, Jan 12, 2017 at 3:27 PM, Kees Cook wrote: > On Thu, Jan 12, 2017 at 1:41 PM, Emese Revfy wrote: >> On Tue, 10 Jan 2017 17:09:31 -0800 >> Kees Cook wrote: >> >>> WARNING: vmlinux.o(.text+0x1087e7): Section mismatch in reference from >>> the function rebind_subsystems() to the variable >>>

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-01-12 Thread Kees Cook
On Thu, Jan 12, 2017 at 1:41 PM, Emese Revfy wrote: > On Tue, 10 Jan 2017 17:09:31 -0800 > Kees Cook wrote: > >> WARNING: vmlinux.o(.text+0x1087e7): Section mismatch in reference from >> the function rebind_subsystems() to the variable >> .init.rodata.str:__func__.4400 >> The function rebind_subs

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-01-12 Thread Emese Revfy
On Tue, 10 Jan 2017 17:09:31 -0800 Kees Cook wrote: > WARNING: vmlinux.o(.text+0x1087e7): Section mismatch in reference from > the function rebind_subsystems() to the variable > .init.rodata.str:__func__.4400 > The function rebind_subsystems() references > the variable __initconst __func__.4400.

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-01-10 Thread Kees Cook
On Tue, Jan 10, 2017 at 4:24 PM, Emese Revfy wrote: > 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 positiv

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-01-10 Thread Emese Revfy
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

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-01-03 Thread Kees Cook
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

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2017-01-03 Thread Kees Cook
On Mon, Dec 19, 2016 at 10:24 AM, Laura Abbott wrote: > I gave this a spin on arm64 and it seems to boot up and run okay > with just the "select HAVE_GCC_PLUGIN_INITIFY_INIT_EXIT if GCC_PLUGINS" > added for arm64. The patches could probably use more review but > I think it would be good to just fo

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2016-12-19 Thread Laura Abbott
On 12/16/2016 02:06 PM, Kees Cook wrote: > Hi, > > This is a continuation of Emese Revfy's initify plugin upstreaming. This > is based on her v3, but updated with various fixes from her github tree. > Additionally, I split off the printf attribute fixes and sent those > separately. > > This is th

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2016-12-19 Thread Emese Revfy
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() > T

Re: [PATCH v4 0/4] Introduce the initify gcc plugin

2016-12-16 Thread Kees Cook
On Fri, Dec 16, 2016 at 2:06 PM, Kees Cook wrote: > Hi, > > This is a continuation of Emese Revfy's initify plugin upstreaming. This > is based on her v3, but updated with various fixes from her github tree. > Additionally, I split off the printf attribute fixes and sent those > separately. > > Th

[PATCH v4 0/4] Introduce the initify gcc plugin

2016-12-16 Thread Kees Cook
Hi, This is a continuation of Emese Revfy's initify plugin upstreaming. This is based on her v3, but updated with various fixes from her github tree. Additionally, I split off the printf attribute fixes and sent those separately. This is the initify gcc plugin. The kernel already has a mechanism