From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Dan Bonachea <bonachead@comcast.net>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: PROBLEM: pthread-safety bug in write(2) on Linux 2.6.x
Date: Thu, 13 Apr 2006 15:33:49 +1000 [thread overview]
Message-ID: <443DE2BD.1080103@yahoo.com.au> (raw)
In-Reply-To: <20060412214613.404cf49f.akpm@osdl.org>
Andrew Morton wrote:
> OK, there _might_ be a real-world case: threads appending logging
> information to a flat file. Trivially workable-around with a userspace
> lock, or by switching to stdio (same thing).
>
> Yes, really we should fix it. But it's not worth adding more overhead to
> do so. So the fix would involve widespread (but simple) change, to draw
> that f_pos update inside i_mutex.
Didn't Linus explicitly made the decision not to add synchronisation for
writes with the same file?
http://groups.google.com/group/fa.linux.kernel/msg/ef66c762e737bab7?hl=en&
Is the closest I could find, but I'm sure he said something similar,
specifically about write(2) vs write(2).
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-04-13 7:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 1:45 PROBLEM: pthread-safety bug in write(2) on Linux 2.6.x Dan Bonachea
2006-04-13 2:10 ` Alistair John Strachan
2006-04-13 4:46 ` Andrew Morton
2006-04-13 5:33 ` Nick Piggin [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=443DE2BD.1080103@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=bonachead@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 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.