public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "David Wragg" <dpw@doc.ic.ac.uk>, <tytso@mit.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: What protects f_pos?
Date: Sun, 12 Nov 2000 14:27:54 -0800	[thread overview]
Message-ID: <NCBBLIEPOCNJOAEKBEAKKENGLNAA.davids@webmaster.com> (raw)
In-Reply-To: <y7raeb69cmg.fsf@sytry.doc.ic.ac.uk>


> 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

	Suppose you had a multithreaded program that used a configuration file with
a group of fixed-length blocks indicating what work it had to do. Each
thread read a block from the file and then did the work. One might think
that there's no need to protect the file descriptor with a mutex.

	DS

-
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/

  reply	other threads:[~2000-11-12 22:28 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
2000-11-12 22:27     ` David Schwartz [this message]
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=NCBBLIEPOCNJOAEKBEAKKENGLNAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=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