From: fche@redhat.com (Frank Ch. Eigler)
To: "Michael K. Edwards" <medwards.linux@gmail.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Bodo Eggert" <7eggert@gmx.de>,
"Eric Dumazet" <dada1@cosmosbay.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: sys_write() racy for multi-threaded append?
Date: 16 Mar 2007 12:43:47 -0400 [thread overview]
Message-ID: <y0mhcsldtq4.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <f2b55d220703141309l20f907c4t6d0bb7dcef724947@mail.gmail.com>
"Michael K. Edwards" <medwards.linux@gmail.com> writes:
> Thanks Alan, this is really helpful -- I'll see if I can figure out
> kprobes. It is not immediately obvious to me how to use them to
> trace function calls in userspace, but I'll read up.
kprobes does not work with userspace. We in systemtap land have been
pushing for such an extension, and primarily IBM folks have been
writing one that would be acceptable for LKML.
> [...] There doesn't seem to be an arch/arm/kernel/kprobes.c, and
> I'm not sure I have the skill to write one. On the other hand,
> ltrace manages something similar (through libelf), and I can trace
> ltrace's ptrace activity with strace, so maybe I can clone that.
> :-)
Efforts are underway to port kprobes to ARM.
Both these efforts may be tracked on the public systemtap mailing list.
- FChE
next prev parent reply other threads:[~2007-03-16 16:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7WzUo-1zl-21@gated-at.bofh.it>
[not found] ` <7WAx2-2pg-21@gated-at.bofh.it>
[not found] ` <7WAGF-2Bx-9@gated-at.bofh.it>
[not found] ` <7WB07-3g5-33@gated-at.bofh.it>
[not found] ` <7WBt7-3SZ-23@gated-at.bofh.it>
2007-03-12 7:53 ` sys_write() racy for multi-threaded append? Bodo Eggert
2007-03-12 16:26 ` Michael K. Edwards
2007-03-12 18:48 ` Bodo Eggert
2007-03-13 0:46 ` Michael K. Edwards
2007-03-13 2:24 ` Alan Cox
2007-03-13 7:25 ` Michael K. Edwards
2007-03-13 7:42 ` David Miller
2007-03-13 16:24 ` Michael K. Edwards
2007-03-13 17:59 ` Michael K. Edwards
2007-03-13 19:09 ` Christoph Hellwig
2007-03-13 23:40 ` Michael K. Edwards
2007-03-14 0:09 ` Michael K. Edwards
2007-03-13 13:15 ` Alan Cox
2007-03-14 20:09 ` Michael K. Edwards
2007-03-16 16:43 ` Frank Ch. Eigler [this message]
2007-03-16 17:25 ` Alan Cox
2007-03-13 14:00 ` David M. Lloyd
2007-03-08 23:08 Michael K. Edwards
2007-03-08 23:43 ` Eric Dumazet
2007-03-08 23:57 ` Michael K. Edwards
2007-03-09 0:15 ` Eric Dumazet
2007-03-09 0:45 ` Michael K. Edwards
2007-03-09 1:34 ` Benjamin LaHaise
2007-03-09 12:19 ` Michael K. Edwards
2007-03-09 13:44 ` Eric Dumazet
2007-03-09 14:10 ` Alan Cox
2007-03-09 14:59 ` Benjamin LaHaise
2007-03-10 6:43 ` Michael K. Edwards
2007-03-09 5:53 ` Eric Dumazet
2007-03-09 11:52 ` Michael K. Edwards
2007-03-09 0:43 ` Alan Cox
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=y0mhcsldtq4.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=7eggert@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=medwards.linux@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).