linux-kernel - Re: [PATCH] uprobes/core: handle breakpoint and signal step exception.

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: <20120228142731.GB15700@elte.hu>
Date:	Tue, 28 Feb 2012 15:27:31 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Christoph Hellwig <hch@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Anton Arapov <anton@...hat.com>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>,
	Jim Keniston <jkenisto@...ux.vnet.ibm.com>,
	Jiri Olsa <jolsa@...hat.com>, Josh Stone <jistone@...hat.com>
Subject: Re: [PATCH] uprobes/core: handle breakpoint and signal step
 exception.


* Srikar Dronamraju <srikar@...ux.vnet.ibm.com> wrote:

> > > The current unregistering thread waits till all other 
> > > threads that have hit a breakpoint to acquire the 
> > > uprobes_treelock before the uprobe is removed from the 
> > > rbtree.
> > 
> > s/is removed/are removed
> > 
> > ?
> > 
> 
> At a time, we are unregistering just one probe,(atleast for 
> now.) Wondering if "before uprobes are remove from rbtree." 
> sounds as if more than one uprobe is being removed at one 
> instance.

The sentence still does not parse:

  " X waits until Ys that have done Z before A is removed from
    the rbtree"

Did you want to say:

" The current unregistering thread waits till all other
  threads have hit a breakpoint, to acquire the
  uprobes_treelock before the uprobe is removed from the
  rbtree. "

(I have removed 'that' and added a comma.)

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/