linux-kernel - Re: [PATCH] drivers: staging: comedi: Add ftrace support

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170719142106.GA30753@kroah.com>
Date:   Wed, 19 Jul 2017 16:21:06 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Piotr Gregor <piotrgregor@...ncme.org>
Cc:     Ian Abbott <abbotti@....co.uk>,
        H Hartley Sweeten <hsweeten@...ionengravers.com>,
        linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org
Subject: Re: [PATCH] drivers: staging: comedi: Add ftrace support

On Wed, Jul 19, 2017 at 02:57:28PM +0100, Piotr Gregor wrote:
> + * Id : Description
> + * 0	Enter the interrupt of amplc_dio200_common
> + * 1	Called from same ISR of amplc_dio200_common if IRQ is handled

That is a very device-specific tracepoint, do we really want each driver
to be able to set these up?

Why can't ftrace handle this type of thing instead?

thanks,

greg k-h