linux-kernel - Enabling trace points during module load/init

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-next>] [day] [month] [year] [list]

Message-ID: <ad6fb376-4fa8-3001-8cc9-7e0a41393616@vodafone.de>
Date:   Wed, 7 Dec 2016 09:27:21 +0100
From:   Christian König <deathsimple@...afone.de>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Alex Deucher <alexander.deucher@....com>
Subject: Enabling trace points during module load/init

Hi everone,

I'm the co-maintainer of the AMD GFX drivers in the upstream kernel and 
yesterday I ran into the problem that I need to enable some trace points 
during module load/init.

We had that issue quite a bunch of times before, but so far never had 
the time or patience to figure out how to enable this properly. So we 
always ended up adding printk() into our code additionally to the 
existing trace points to figure out what the driver does during startup.

But this time I started to Google a bit and figured out that Steven 
Rostedt already had that issue solved years ago, but never pushed it 
upstream. Asking Steven why the absolutely surprising answer was that it 
was dropped because nobody spoke up and said that this was an useful 
feature.

So here I'm absolutely confirming that this is an useful feature and we 
could really make good use of it. Also feel free to CC me for reviews 
and/or testing.

Best regards,
Christian.