mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Oleg Drokin <green@namesys.com>,
	David Ford <david+powerix@blue-labs.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Current NFS issues (2.5.59)
Date: Wed, 12 Feb 2003 01:05:08 +0100	[thread overview]
Message-ID: <15945.36788.945931.141582@charged.uio.no> (raw)
In-Reply-To: <15945.30044.444455.162630@notabene.cse.unsw.edu.au>

>>>>> " " == Neil Brown <neilb@cse.unsw.edu.au> writes:


     > Feb 12 09:11:35 kamen kernel: RPC: udp_data_ready...  Feb 12
     > 09:11:35 kamen kernel: RPC: udp_data_ready client e6219000 Feb

     > which seems to suggest that the reply is coming back from the
     > server (RPC: udp_data_ready) but there is no sign of the client
     > getting it...

On the contrary. The above shows that the client is indeed receiving
some data, but for some reason it is not accepting that data as a
valid reply. It looks as if either skb_recv_datagram() or
xprt_lookup_rqst() is failing.

BTW: I'm still not seeing any such trouble with these loopback mounts
on my own machine. Could it be an SMP problem?

Cheers,
  Trond

  reply	other threads:[~2003-02-11 23:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-09 23:18 David Ford
2003-02-11  4:05 ` Neil Brown
2003-02-11  7:00   ` Oleg Drokin
2003-02-11 12:23     ` Trond Myklebust
2003-02-11 13:31       ` Oleg Drokin
2003-02-11 22:12         ` Neil Brown
2003-02-12  0:05           ` Trond Myklebust [this message]
2003-02-12  0:20             ` David Ford
2003-02-11 16:55   ` David Ford
2003-02-11 22:32     ` Neil Brown

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=15945.36788.945931.141582@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=david+powerix@blue-labs.org \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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®