mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Gregory Giguashvili <Gregoryg@ParadigmGeo.com>
Cc: "Linux Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Subject: RE: O_SYNC option doesn't work (2.4.18-3)
Date: Wed, 7 Aug 2002 19:19:07 +0200	[thread overview]
Message-ID: <15697.22155.257411.150056@charged.uio.no> (raw)
In-Reply-To: <EE83E551E08D1D43AD52D50B9F511092E114E0@ntserver2>

>>>>> " " == Gregory Giguashvili <Gregoryg@ParadigmGeo.com> writes:

    >> The latter are found on ftp.kernel.org and mirrors...
     > Are you saying that this problem is non-existent in the latest
     > kernel patches? Can you, please, point to at least one of them?

No. I said that reporting bugs on RedHat-specific kernels should be
done to RedHat rather than to this list.

As for O_SYNC, AFAICS there are no bugs in the standard
kernel. However if you are thinking that O_SYNC means that you can
write simultaneously to the same file from 2 different clients, then
the answer is "the NFS protocol won't allow you to do that".
The *only* method of ensuring cache consistency in such a case is to
use POSIX file locking.

Cheers,
  Trond

  reply	other threads:[~2002-08-07 17:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-07 17:31 Gregory Giguashvili
2002-08-07 17:19 ` Trond Myklebust [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08 14:57 Gregory Giguashvili
2002-08-08 15:37 ` Daniel Forrest
2002-08-08 13:48 Jesse Pollard
     [not found] <fa.jepn5rv.uiqrqe@ifi.uio.no>
     [not found] ` <fa.gkqj0av.c661ad@ifi.uio.no>
2002-08-08  7:11   ` Giacomo Catenazzi
2002-08-08  8:06     ` Willy Tarreau
2002-08-08 12:36       ` Alan Cox
2002-08-07 20:48 Jesse Pollard
2002-08-08 10:07 ` Martin Brulisauer
2002-08-07 19:30 Gregory Giguashvili
2002-08-08 13:42 ` Trond Myklebust
2002-08-07 19:24 Gregory Giguashvili
2002-08-07 19:38 ` Trond Myklebust
2002-08-07 21:55 ` Alan Cox
2002-08-07 18:54 Gregory Giguashvili
2002-08-07 18:13 ` Trond Myklebust
2002-08-07 18:39 Gregory Giguashvili
2002-08-07 17:43 ` Trond Myklebust
2002-08-07 18:15 Jesse Pollard
2002-08-07 17:24 Gregory Giguashvili
2002-08-07 16:31 ` Trond Myklebust
2002-08-07 17:17 Gregory Giguashvili
2002-08-07 16:24 ` Trond Myklebust
2002-08-07 20:20   ` Benjamin LaHaise

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=15697.22155.257411.150056@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=Gregoryg@ParadigmGeo.com \
    --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®