lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 29 Jan 2016 09:45:20 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: Alexander Potapenko <glider@...gle.com> Cc: Andrey Konovalov <adech.fo@...il.com>, Christoph Lameter <cl@...ux.com>, Dmitriy Vyukov <dvyukov@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>, Andrey Ryabinin <ryabinin.a.a@...il.com>, kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH v1 4/8] arch, ftrace: For KASAN put hard/soft IRQ entries into separate sections On Fri, 29 Jan 2016 12:59:13 +0100 Alexander Potapenko <glider@...gle.com> wrote: > On the other hand, this will require including <linux/irq.h> into > various files that currently use __irq_section. > But that header has a comment saying: > > /* > * Please do not include this file in generic code. There is currently > * no requirement for any architecture to implement anything held > * within this file. > * > * Thanks. --rmk > */ > > Do we really want to put anything into that header? > What about interrupt.h? It's just weird to have KSAN needing to pull in ftrace.h for irq work. -- Steve
Powered by blists - more mailing lists