Re: [PATCH v4 4/7] arch, ftrace: For KASAN put hard/soft IRQ entries into separate sections

2016-03-02 Thread Steven Rostedt
On Fri, 26 Feb 2016 17:48:44 +0100 Alexander Potapenko wrote: > KASAN needs to know whether the allocation happens in an IRQ handler. > This lets us strip everything below the IRQ entry point to reduce the > number of unique stack traces needed to be stored. > > Move the definition of __irq_entr

Re: [PATCH v4 4/7] arch, ftrace: For KASAN put hard/soft IRQ entries into separate sections

2016-02-26 Thread kbuild test robot
Hi Alexander, [auto build test ERROR on tip/x86/core] [also build test ERROR on v4.5-rc5] [cannot apply to next-20160226] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Alexander-Potapenko/SLA

[PATCH v4 4/7] arch, ftrace: For KASAN put hard/soft IRQ entries into separate sections

2016-02-26 Thread Alexander Potapenko
KASAN needs to know whether the allocation happens in an IRQ handler. This lets us strip everything below the IRQ entry point to reduce the number of unique stack traces needed to be stored. Move the definition of __irq_entry to so that the users don't need to pull in . Also introduce the __softi