From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Birger Lammering <b.lammering@science-computing.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: more tcpdumpinfo for nfs3 problem: aix-server
Date: Wed, 9 Jan 2002 17:04:28 +0100 [thread overview]
Message-ID: <15420.27148.80553.930142@charged.uio.no> (raw)
In-Reply-To: <15420.23686.566719.128899@stderr.science-computing.de>
In-Reply-To: <15418.55750.210978.737165@stderr.science-computing.de> <15418.63966.866222.749974@charged.uio.no> <15420.23686.566719.128899@stderr.science-computing.de>
> Strange situation: both, you and the amd-guys, think the bug is
> somewhere in the code of the other.
Although I won't exclude the fact that there may be a kernel bug, as
long as this condition is not reproducible with anything other than
amd, I'm going to need a lot of convincing.
> And I have no idea, how to circle in the
> bug.... (Kernel-debugging???)
That depends a lot on what it is amd actually does. Is it for instance
acting as a proxy between the client and the server, or in any other
way touching those packets?
I've never used amd, so I frankly have no idea what sort of special
thing it does on top of the standard NFS client. That's why I'd prefer
that Ion look into it.
If it turns out that a proper bugreport can be compiled that points to
a kernel NFS client problem, I'll be happy to help fix it. As things
stand, however, I am unable to reproduce any such problems on my own
setups and I have no spare time at the moment to start messing with
amd myself.
Cheers,
Trond
next prev parent reply other threads:[~2002-01-09 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 11:36 Birger Lammering
2002-01-08 13:53 ` Trond Myklebust
2002-01-09 16:04 ` Trond Myklebust [this message]
2002-01-09 15:06 ` Birger Lammering
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=15420.27148.80553.930142@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=b.lammering@science-computing.de \
--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®