linux-kernel - Re: [PATCH] ptrace: add ability to get clear_tid

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]

Date:	Wed, 8 Feb 2012 23:20:19 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Pedro Alves <palves@...hat.com>,
	Pavel Emelyanov <xemul@...allels.com>,
	Jan Kratochvil <jan.kratochvil@...hat.com>,
	Tejun Heo <tj@...nel.org>, Andrew Vagin <avagin@...nvz.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ptrace: add ability to get clear_tid_address

On Wed, Feb 08, 2012 at 08:02:50PM +0100, Oleg Nesterov wrote:
> > Right, as I said.  :-)  I saw that a watchpoint trap isn't reported either
> > for the CLONE_CHILD_SETTID case (that is, within clone, when the kernel
> > writes the tid to the memory address passed in to the clone syscall).
> 
> Yes. But in this case the new thread has no bps even if it is auto-
> attached.
> 
> IOW, I think that hw bp can detect the write from the kernel space,
> but I didn't check.

yes, that's how kgdb work (if only I'm not missing something obvious)

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