All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Tucker <tom@opengridcomputing.com>
To: <mjt@tls.msk.ru>, <linux-nfs@vger.kernel.org>
Subject: Re: 2.6.24: RPC: bad TCP reclen 0x00020090 (large)
Date: Fri, 14 Mar 2008 12:28:19 -0500	[thread overview]
Message-ID: <C4001FE3.3BDB9%tom@opengridcomputing.com> (raw)


Michael:

>>>>> On Wed, 13 Feb 2008 17:02:53 +0300 Michael Tokarev <mjt@tls.msk.ru> wrote:
>>>>> 
>>>>>> Hello!
>>>>>> 
>>>>>> After upgrading to 2.6.24 (from .23), we're seeing ALOT
>>>>>> of messages like in $subj in dmesg:
>>>>>> 
>>>>>> Feb 13 13:21:39 paltus kernel: RPC: bad TCP reclen 0x00020090 (large)
>>>>>> Feb 13 13:21:46 paltus kernel: printk: 3586 messages suppressed.
>>>>>> Feb 13 13:21:46 paltus kernel: RPC: bad TCP reclen 0x00020090 (large)
>>>>>> Feb 13 13:21:49 paltus kernel: printk: 371 messages suppressed.
>>>>>> Feb 13 13:21:49 paltus kernel: RPC: bad TCP reclen 0x00020090 (large)
>>>>>> Feb 13 13:21:55 paltus kernel: printk: 2979 messages suppressed.
>>>>>> ...
>>>>>> 

Are you seeing this with the latest bits?  I just want to make sure that
this particular close path issue is fixed.

Thanks,
Tom



             reply	other threads:[~2008-03-14 17:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 17:28 Tom Tucker [this message]
2008-03-14 18:57 ` 2.6.24: RPC: bad TCP reclen 0x00020090 (large) Michael Tokarev
     [not found]   ` <47DACA7C.8020807-Gdu+ltImwkhes2APU0mLOQ@public.gmane.org>
2008-03-14 19:06     ` J. Bruce Fields
2008-03-14 19:25       ` Tom Tucker
2008-03-15  0:10         ` J. Bruce Fields
  -- strict thread matches above, loose matches on Subject: below --
2008-02-13 14:02 Michael Tokarev
     [not found] ` <47B2F88D.7080300-Gdu+ltImwkhes2APU0mLOQ@public.gmane.org>
2008-02-18 12:58   ` Andrew Morton
2008-02-18 12:58     ` Andrew Morton
2008-02-18 13:05     ` Michael Tokarev
2008-02-18 21:25     ` Tom Tucker
     [not found]       ` <1203369909.24272.44.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2008-02-18 22:00         ` Tom Tucker
2008-02-18 22:00           ` Tom Tucker

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=C4001FE3.3BDB9%tom@opengridcomputing.com \
    --to=tom@opengridcomputing.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.