From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Petr Vandrovec <petr@vmware.com>,
"bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org"
<bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org>,
Petr Vandrovec <petr@vandrovec.name>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [Bug 13034] printk in xs_tcp_setup_socket needs rate limit ... and delay
Date: Thu, 23 Apr 2009 09:02:07 +0200 [thread overview]
Message-ID: <20090423090207.5d6a1cd9@hyperion.delvare> (raw)
In-Reply-To: <1240447977.9197.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On Wed, 22 Apr 2009 20:52:57 -0400, Trond Myklebust wrote:
> Good! The 5minute idle timeout is the one case where we don't care about
> preserving the port number (because there are no outstanding NFS
> requests to replay to the server).
>
> Jean, are you seeing the same behaviour (i.e. errors only on idle
> timeout), and is the fix working for you?
I didn't hit the problem since I applied your patch, but that was only
yesterday so it's too early to draw statistically valid conclusions.
It is highly possible that the bug was happening on idle timeout, I am
the only user on this machine and I access the NFS mounts only from
times to times.
--
Jean Delvare
prev parent reply other threads:[~2009-04-23 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13034-104@http.bugzilla.kernel.org/>
[not found] ` <200904222049.n3MKnxZi019947@demeter.kernel.org>
[not found] ` <200904222049.n3MKnxZi019947-jEpIWWs/U2wOASNP4CLbKB2eb7JE58TQ@public.gmane.org>
2009-04-22 20:58 ` [Bug 13034] printk in xs_tcp_setup_socket needs rate limit ... and delay Trond Myklebust
[not found] ` <1240433936.9197.9.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-22 22:22 ` Petr Vandrovec
2009-04-23 0:52 ` Trond Myklebust
[not found] ` <1240447977.9197.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-23 7:02 ` Jean Delvare [this message]
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=20090423090207.5d6a1cd9@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=petr@vandrovec.name \
--cc=petr@vmware.com \
--cc=trond.myklebust@fys.uio.no \
/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