From: Eric Whiting <ewhiting@amis.com>
To: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: RPC request error message
Date: Wed, 24 Apr 2002 08:48:13 -0600 [thread overview]
Message-ID: <3CC6C5AD.3048F8D6@amis.com> (raw)
Apr 24 06:16:08 windriver kernel: RPC request reserved 240 but used 244
Apr 24 06:17:58 windriver kernel: RPC request reserved 240 but used 244
Apr 24 06:17:58 windriver kernel: RPC request reserved 52 but used 56
Apr 24 06:34:35 windriver kernel: RPC request reserved 240 but used 244
Apr 24 06:34:35 windriver kernel: RPC request reserved 52 but used 56
I get about 50-200 of these messages each day. Kernel is 2.4.18. I see
this message in one of Neil's recent patches.
+ /* Reset response buffer and release
+ * the reservation.
+ * But first, check that enough space was reserved
+ * for the reply, otherwise we have a bug!*/
+
+ if ((rqstp->rq_resbuf.len<2) > rqstp->rq_reserved)
+ printk(KERN_ERR "RPC request reserved %d but used
%d\n",
+ rqstp->rq_reserved,
+ rqstp->rq_resbuf.len<2);
+
Is anyone else seeing this?
eric
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-04-24 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 14:48 Eric Whiting [this message]
2002-04-24 23:00 ` RPC request error message 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=3CC6C5AD.3048F8D6@amis.com \
--to=ewhiting@amis.com \
--cc=nfs@lists.sourceforge.net \
/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.