From: "David S. Miller" <davem@redhat.com>
To: trond.myklebust@fys.uio.no
Cc: Nix <nix@esperi.demon.co.uk>,
ultralinux@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: strange sparc64 -> i586 intermittent but reproducible NFS write errors to one and only one fs
Date: 19 Jan 2003 22:38:34 -0800 [thread overview]
Message-ID: <1043044714.10408.0.camel@rth.ninka.net> (raw)
In-Reply-To: <15915.4574.380686.123067@charged.uio.no>
On Sun, 2003-01-19 at 13:00, Trond Myklebust wrote:
> It sounds rather strange that this particular patch should introduce
> an EIO, but here it is (fresh from BitKeeper)
It is possible in the context of the change causing a miscompile.
Another possibility is just timing differences causing different
sequences of events to occur than before.
next prev parent reply other threads:[~2003-01-20 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 22:56 Nix
2003-01-10 6:57 ` Denis Vlasenko
2003-01-19 20:21 ` Nix
2003-01-19 21:00 ` Trond Myklebust
2003-01-20 6:38 ` David S. Miller [this message]
2003-01-20 20:53 ` Nix
2003-02-03 17:35 ` Nix
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=1043044714.10408.0.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.demon.co.uk \
--cc=trond.myklebust@fys.uio.no \
--cc=ultralinux@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®