From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,
Pavel Emelyanov <xemul@parallels.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Tejun Heo <tj@kernel.org>, Andrew Vagin <avagin@openvz.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ptrace: add ability to get clear_tid_address
Date: Wed, 8 Feb 2012 23:20:19 +0400 [thread overview]
Message-ID: <20120208192019.GM1909@moon> (raw)
In-Reply-To: <20120208190250.GA23163@redhat.com>
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
next prev parent reply other threads:[~2012-02-08 19:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 11:11 [PATCH] ptrace: add ability to get clear_tid_address Andrew Vagin
2012-02-03 16:25 ` Tejun Heo
2012-02-03 16:30 ` Cyrill Gorcunov
2012-02-03 16:41 ` Oleg Nesterov
2012-02-03 16:54 ` Cyrill Gorcunov
2012-02-03 16:45 ` Pavel Emelyanov
2012-02-03 16:51 ` Oleg Nesterov
2012-02-07 20:07 ` Pedro Alves
2012-02-07 20:56 ` Cyrill Gorcunov
2012-02-07 21:15 ` Pedro Alves
2012-02-07 21:51 ` Cyrill Gorcunov
2012-02-08 12:30 ` Pedro Alves
2012-02-08 12:42 ` Cyrill Gorcunov
2012-02-08 17:31 ` Oleg Nesterov
2012-02-08 18:04 ` Pedro Alves
2012-02-08 19:02 ` Oleg Nesterov
2012-02-08 19:20 ` Cyrill Gorcunov [this message]
2012-02-08 19:21 ` Jan Kratochvil
2012-02-08 19:42 ` Pedro Alves
2012-02-08 13:41 ` Andrew Vagin
2012-02-08 18:12 ` Jan Kratochvil
2012-02-10 3:02 ` Jamie Lokier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120208192019.GM1909@moon \
--to=gorcunov@openvz.org \
--cc=avagin@openvz.org \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=palves@redhat.com \
--cc=tj@kernel.org \
--cc=xemul@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.