linux-kernel - Re: systemtap broken by removal of register_timer

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]

Date:	Wed, 3 Apr 2013 14:49:53 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	"Frank Ch. Eigler" <fche@...hat.com>
Cc:	Mel Gorman <mgorman@...e.de>, Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	SystemTap <systemtap@...rceware.org>
Subject: Re: systemtap broken by removal of register_timer_hook

2013/4/3 Frank Ch. Eigler <fche@...hat.com>:
> Frederic Weisbecker <fweisbec@...il.com> writes:
>
>> [...]
>> Sometimes I don't mind keeping around code in the kernel for out of
>> tree users, depending on the case. But in this specific matter we have
>> more standard ways to do this kind of hook: kprobes, static
>> tracepoints. A tracepoint on the timer tick would be useful BTW, and
>> you could reuse it.
>
> Thanks for noticing!  IMO kprobes would be too heavyweight for this.
> A new static tracepoint would be fine, especially if it passes the
> same pt_regs* pointer as the former hook did.

Sounds good, would you like to propose a version? We are also
interested in a timer tick event tracepoint for dynticks debugging.

Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/