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: <20130124154159.GB32071@gmail.com>
Date:	Thu, 24 Jan 2013 16:41:59 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Anton Arapov <anton@...hat.com>,
	Christoph Hellwig <hch@...radead.org>,
	Josh Stone <jistone@...hat.com>,
	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] uprobes: pre-filtering


* Oleg Nesterov <oleg@...hat.com> wrote:

> On 01/24, Ingo Molnar wrote:
> >
> > * Oleg Nesterov <oleg@...hat.com> wrote:
> >
> > > Ingo, please pull from
> > >
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes/core
> > >
> > > Mostly pre-filtering. This needs more work and perhaps more functionality.
> > > In particular, perhaps dup_mmap() should remove the unwanted breakpoints.
> > > And we can add more ->filter() hooks to, say, speedup uprobe_register().
> > > Plus we can do some optimizations to avoid register_for_each_vma() in
> > > case when we know that all mm's were previously acked/nacked.
> >
> > The kernel side looks good to me - but how does 'perf 
> > uprobe' make use of it in practice, how can I test it?
> 
> Unfortunately, currently there is no in-kernel user of 
> pre-filtering.
> 
> 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.

Would be nice to get something minimal/simple going, so that it 
can be tested, etc.

Thanks,

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