linux-kernel - [RFC][PATCH 0/4] tracing: event filtering

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: <1237271002.8033.148.camel@charm-linux>
Date:	Tue, 17 Mar 2009 01:23:22 -0500
From:	Tom Zanussi <tzanussi@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Steven Rostedt <rostedt@...dmis.org>,
	Frédéric Weisbecker <fweisbec@...il.com>
Subject: [RFC][PATCH 0/4] tracing: event filtering

Hi,

This patchset is a first attempt at adding filtering to the
event-tracing infrastructure.

The filtering itself seems to work ok, as far as I've been able to test
it, but I'm still battling with getting the ring-buffer to do what I
want (discarding events, see patch 2) so am hoping someone more familiar
with the ring buffer can point me in the right direction before I do any
more work on it.

Another specific thing it would be good to get comments on would be how
to allow the user to unambiguously specify a field name in a filter when
there are duplicate field names for an event, as mentioned in patch 1.

Of course, any comments about the rest of the interface and code are
also welcome...

Thanks,

Tom

--
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/