linux-kernel - Re: [PATCH] ftrace: add an fsync tracer

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: <c62985530811060528r5bff8c1ct9487936b978d6ecb@mail.gmail.com>
Date:	Thu, 6 Nov 2008 14:28:34 +0100
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Peter Zijlstra" <peterz@...radead.org>
Cc:	"Arjan van de Ven" <arjan@...radead.org>,
	"Steven Rostedt" <rostedt@...dmis.org>,
	linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: Re: [PATCH] ftrace: add an fsync tracer

2008/11/6 Peter Zijlstra <peterz@...radead.org>:
> Please work on getting something like a syscall tracer, or lttng like
> event tracer.
>
> Both of those should be able to find such badness, but are also able to
> diagnose many more issues.


BTW. Why not adding a kind of tracer_ctrl callback on the
struct_tracer? This way we could add some custom
options on the iter_ctrl file that could be transmitted to the current_tracer.

For example considering a syscall tracer.
By default if we don't write anything on iter_ctrl, it traces all
syscalls. But if we do:
echo fsync > iter_ctrl
Only the fsync call will be traced (unused tracepoint would be disabled).

A tracer just have to implement this new callback and transmit the
options it support.
--
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/