From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: linux-next@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH next-20090316] sunrpc: fix build breakage
Date: Mon, 16 Mar 2009 09:04:40 -0400 [thread overview]
Message-ID: <1237208680.7229.14.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20090316125140.GA3095@orion>
On Mon, 2009-03-16 at 15:51 +0300, Alexander Beregalov wrote:
> net/sunrpc/clnt.c: In function 'call_bind_status':
> net/sunrpc/clnt.c:994: error: 'struct rpc_task' has no member named
> 'tk_pid'
> net/sunrpc/clnt.c: In function 'call_connect_status':
> net/sunrpc/clnt.c:1051: error: 'struct rpc_task' has no member named
> 'tk_pid'
>
> rpc_task has tk_pid if RPC_DEBUG is defined.
>
> Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
> ---
>
> net/sunrpc/clnt.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
> index efd0c7b..68cb91a 100644
> --- a/net/sunrpc/clnt.c
> +++ b/net/sunrpc/clnt.c
> @@ -990,7 +990,7 @@ call_bind_status(struct rpc_task *task)
> return;
> default:
> if (net_ratelimit())
> - printk("RPC: %5u unrecognized rpcbind error (%d)\n",
> + dprintk("RPC: %5u unrecognized rpcbind error (%d)\n",
> task->tk_pid, -task->tk_status);
> }
>
> @@ -1047,7 +1047,7 @@ call_connect_status(struct rpc_task *task)
> break;
> default:
> if (net_ratelimit())
> - printk("RPC: %5u unrecognized connect error (%d)\n",
> + dprintk("RPC: %5u unrecognized connect error (%d)\n",
> task->tk_pid, status);
> rpc_exit(task, -EIO);
> }
No, that's not right. The intention is to always report errors that are
fatal and are due to unforeseen circumstances. Your patch means that
those reports are suppressed entirely when RPC_DEBUG is undefined.
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2009-03-16 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 12:51 [PATCH next-20090316] sunrpc: fix build breakage Alexander Beregalov
2009-03-16 13:04 ` Trond Myklebust [this message]
[not found] ` <1237208680.7229.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-03-18 15:56 ` Randy Dunlap
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=1237208680.7229.14.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=a.beregalov@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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