From: Daniel Jacobowitz <dan@debian.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, drepper@redhat.com,
tglx@linutronix.de, arjan@infradead.org, dsingleton@mvista.com
Subject: Re: [patch 0/5] lightweight robust futexes: -V1
Date: Fri, 17 Feb 2006 16:59:33 -0500 [thread overview]
Message-ID: <20060217215933.GA1874@nevyn.them.org> (raw)
In-Reply-To: <20060215221434.GA20104@elte.hu>
On Wed, Feb 15, 2006 at 11:14:34PM +0100, Ingo Molnar wrote:
> > Why do we need sys_get_robust_list(other task)?
>
> just for completeness for debuggers - when i added the TLS syscalls
> debugging people complained that there was no easy way to query the TLS
> settings of a thread. I didnt want to add yet another ptrace op - but
> maybe that's the right solution? ptrace is a bit clumsy for things like
> this - the task might not be ptrace-able, while querying the list head
> is such an easy thing.
If it isn't ptraceable, then why should we need to ask the kernel for a
pointer into its memory? Except maybe for attacking it :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-17 21:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 15:17 [patch 0/5] lightweight robust futexes: -V1 Ingo Molnar
2006-02-15 15:22 ` Ingo Molnar
2006-02-15 17:35 ` Andi Kleen
2006-02-15 17:50 ` Ulrich Drepper
2006-02-15 18:42 ` Andi Kleen
2006-02-15 19:49 ` Christopher Friesen
2006-02-15 20:02 ` Andi Kleen
2006-02-15 20:13 ` Antonio Vargas
2006-02-15 20:25 ` Andi Kleen
2006-02-15 20:59 ` Ingo Molnar
2006-02-15 20:43 ` Ingo Molnar
2006-02-15 19:05 ` Daniel Walker
2006-02-15 19:11 ` Arjan van de Ven
2006-02-15 19:13 ` Daniel Walker
2006-02-15 21:31 ` Ingo Molnar
2006-02-16 15:43 ` Daniel Walker
2006-02-15 21:45 ` Andrew Morton
2006-02-15 22:14 ` Ingo Molnar
2006-02-17 21:59 ` Daniel Jacobowitz [this message]
2006-02-16 3:57 ` Darren Hart
2006-02-16 14:58 ` Johannes Stezenbach
2006-02-16 17:20 ` Ingo Molnar
2006-02-16 19:04 ` Daniel Walker
2006-02-17 9:09 ` Avi Kivity
2006-02-17 19:55 ` Johannes Stezenbach
2006-02-17 20:02 ` Arjan van de Ven
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=20060217215933.GA1874@nevyn.them.org \
--to=dan@debian.org \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=drepper@redhat.com \
--cc=dsingleton@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.