From: Paul Mundt <lethal@linux-sh.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/sunrpc/clnt.c compile fix
Date: Thu, 9 Oct 2003 12:54:28 -0400 [thread overview]
Message-ID: <20031009165428.GA12093@linux-sh.org> (raw)
In-Reply-To: <16261.37335.822076.188805@charged.uio.no>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
On Thu, Oct 09, 2003 at 12:50:31PM -0400, Trond Myklebust wrote:
> It's not a true process pid, but more of a tag on each struct
> rpc_task. It turns out to be more helpful when you are tracing the
> (d|)printk() debugging info, since a process may have several rpc_task
> in flight at any point in time.
>
Sounds reasonable. Does this look ok?
--- linux-sh-2.6.0-test7.orig/net/sunrpc/clnt.c Thu Oct 9 09:42:45 2003
+++ linux-sh-2.6.0-test7/net/sunrpc/clnt.c Thu Oct 9 12:53:05 2003
@@ -961,19 +961,19 @@
case RPC_SUCCESS:
return p;
case RPC_PROG_UNAVAIL:
- printk(KERN_WARNING "RPC: %4d call_verify: program %u is unsupported by server %s\n",
- task->tk_pid, (unsigned int)task->tk_client->cl_prog,
+ printk(KERN_WARNING "RPC: call_verify: program %u is unsupported by server %s\n",
+ (unsigned int)task->tk_client->cl_prog,
task->tk_client->cl_server);
goto out_eio;
case RPC_PROG_MISMATCH:
- printk(KERN_WARNING "RPC: %4d call_verify: program %u, version %u unsupported by server %s\n",
- task->tk_pid, (unsigned int)task->tk_client->cl_prog,
+ printk(KERN_WARNING "RPC: call_verify: program %u, version %u unsupported by server %s\n",
+ (unsigned int)task->tk_client->cl_prog,
(unsigned int)task->tk_client->cl_vers,
task->tk_client->cl_server);
goto out_eio;
case RPC_PROC_UNAVAIL:
- printk(KERN_WARNING "RPC: %4d call_verify: proc %p unsupported by program %u, version %u on server %s\n",
- task->tk_pid, task->tk_msg.rpc_proc,
+ printk(KERN_WARNING "RPC: call_verify: proc %p unsupported by program %u, version %u on server %s\n",
+ task->tk_msg.rpc_proc,
task->tk_client->cl_prog,
task->tk_client->cl_vers,
task->tk_client->cl_server);
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-09 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 16:13 [PATCH] net/sunrpc/clnt.c compile fix Paul Mundt
2003-10-09 16:33 ` Geert Uytterhoeven
2003-10-09 16:37 ` Trond Myklebust
2003-10-09 16:40 ` Paul Mundt
2003-10-09 16:50 ` Trond Myklebust
2003-10-09 16:54 ` Paul Mundt [this message]
2003-10-09 16:57 ` Trond Myklebust
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=20031009165428.GA12093@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--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