linux-kernel - Re: [GIT PULL] uprobes: pre-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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <510169EA.3070506@redhat.com>
Date:	Thu, 24 Jan 2013 09:05:46 -0800
From:	Josh Stone <jistone@...hat.com>
To:	Oleg Nesterov <oleg@...hat.com>
CC:	Ingo Molnar <mingo@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	Anton Arapov <anton@...hat.com>,
	Christoph Hellwig <hch@...radead.org>,
	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] uprobes: pre-filtering

On 01/24/2013 07:40 AM, Oleg Nesterov wrote:
> I'll try to implement the pid-base filtering at least for
> tracing/uprobe_events, but this needs a time. Not only I am not familiar
> with this code, I am not sure how this interface should actually look.
> And I agree, perf should be able to use it somehow, perhaps at least
> to allow to probe a single task/mm.

Even without changing perf's interface, it already has constraints for
its child processes (versus --all-cpus) or for specific pid/tid/uid.
Pre-filtering could help enforce and optimize those constraints.
--
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/