From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
Pavel Emelianov <xemul@parallels.com>,
"neilb@suse.de" <neilb@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bfields@fieldses.org" <bfields@fieldses.org>,
"skinsbursky@openvz.org" <skinsbursky@openvz.org>
Subject: Re: [PATCH] RPC: return task->tk_status from rpc_wait_for_completion_task() in case of successfull task completion
Date: Tue, 15 Mar 2011 20:36:38 +0300 [thread overview]
Message-ID: <4D7FA3A6.4000305@parallels.com> (raw)
In-Reply-To: <1300199215.14093.1.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
15.03.2011 17:26, Trond Myklebust =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
> On Tue, 2011-03-15 at 17:20 +0300, Stanislav Kinsbursky wrote:
>> Some NFS and NLM routines doesn't check RPC task tk_status if
>> rpc_wait_for_completion_task() returned 0 but have to.
>
> Examples please. I'm not aware of any such cases.
>
> Cheers
> Trond
>
You are right. I was confused with different logic for NSFv4, NLM and N=
=46Sv3.
Drop the patch.
Sorry.
--=20
Best regards,
Stanislav Kinsbursky
prev parent reply other threads:[~2011-03-15 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 14:20 [PATCH] RPC: return task->tk_status from rpc_wait_for_completion_task() in case of successfull task completion Stanislav Kinsbursky
[not found] ` <20110315141951.16564.72417.stgit-bi+AKbBUZKagILUCTcTcHdKyNwTtLsGr@public.gmane.org>
2011-03-15 14:26 ` Trond Myklebust
[not found] ` <1300199215.14093.1.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
2011-03-15 17:36 ` Stanislav Kinsbursky [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=4D7FA3A6.4000305@parallels.com \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=skinsbursky@openvz.org \
--cc=xemul@parallels.com \
/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;
as well as URLs for NNTP newsgroup(s).