From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Dan Bonachea <bonachead@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: pthread-safety bug in write(2) on Linux 2.6.x
Date: Thu, 13 Apr 2006 03:10:27 +0100 [thread overview]
Message-ID: <200604130310.27560.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <6.2.5.6.2.20060412173852.033dbb90@cs.berkeley.edu>
On Thursday 13 April 2006 02:45, Dan Bonachea wrote:
> Hi - I believe I've discovered a thread-safety bug in the Linux 2.6.x
> kernel implementation of write(2).
Hi, let's get the obvious out of the way first.
Is this reproducible on a current -stable, non-vendor kernel?
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-04-13 2:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 1:45 Dan Bonachea
2006-04-13 2:10 ` Alistair John Strachan [this message]
2006-04-13 4:46 ` Andrew Morton
2006-04-13 5:33 ` Nick Piggin
2006-04-13 15:01 ` Linus Torvalds
2006-04-13 15:28 ` Linus Torvalds
2006-04-14 10:20 ` Nikita Danilov
2006-04-13 21:50 ` Alan Cox
2006-04-13 22:06 ` Dan Bonachea
2006-04-13 23:03 ` Linus Torvalds
2006-04-13 23:11 ` Alan Cox
2006-04-13 23:19 ` Linus Torvalds
2006-04-13 22:40 ` Linus Torvalds
2006-04-13 23:05 ` Alan Cox
2006-04-13 23:06 ` Linus Torvalds
2006-04-13 23:11 ` Linus Torvalds
2006-04-13 9:18 ` Dan Bonachea
2006-04-13 9:56 ` Andrew Morton
2006-04-13 10:28 ` Kyle Moffett
2006-04-13 14:14 ` Jan Engelhardt
2010-12-19 22:45 ` Jens Moser
[not found] <60Z8f-4QA-25@gated-at.bofh.it>
[not found] ` <611Wl-u5-1@gated-at.bofh.it>
[not found] ` <616k2-6Xz-27@gated-at.bofh.it>
2006-04-14 9:14 ` Kai Henningsen
2006-04-27 9:06 Samuel Thibault
2006-04-27 15:23 ` Linus Torvalds
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=200604130310.27560.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=bonachead@comcast.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®