From: David Wragg <dpw@doc.ic.ac.uk>
To: tytso@mit.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: What protects f_pos?
Date: 12 Nov 2000 01:56:39 +0000 [thread overview]
Message-ID: <y7raeb69cmg.fsf@sytry.doc.ic.ac.uk> (raw)
In-Reply-To: <y7r8zqzqt71.fsf@sytry.doc.ic.ac.uk> <200011112354.eABNs0005918@trampoline.thunk.org>
In-Reply-To: tytso@mit.edu's message of "Sat, 11 Nov 2000 18:54:00 -0500"
tytso@mit.edu writes:
> This looks like it's a bug to me.... although if you have multiple
> threads hitting a file descriptor at the same time, you're pretty much
> asking for trouble.
Yes, I haven't been able to come up with an example that might trigger
this that wasn't dubious to begin with. I'll raise this again at a
convenient time during 2.5.
David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-12 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-04 22:16 What protects f_pos? David Wragg
2000-11-11 23:54 ` tytso
2000-11-12 1:56 ` David Wragg [this message]
2000-11-12 22:27 ` David Schwartz
2000-11-13 15:22 ` David Wragg
2000-11-13 15:44 ` Richard B. Johnson
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=y7raeb69cmg.fsf@sytry.doc.ic.ac.uk \
--to=dpw@doc.ic.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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