All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chucklever@gmail.com>
Cc: Libtirpc Devel List <libtirpc-devel@lists.sourceforge.net>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [Libtirpc-devel] [PATCH] Do not skip records with nonblocking connections
Date: Sun, 05 Jun 2011 19:51:46 -0400	[thread overview]
Message-ID: <4DEC1692.6070504@RedHat.com> (raw)
In-Reply-To: <44DFB4C2-AD75-412F-B211-D6DB1B9D2ACE@gmail.com>



On 06/05/2011 06:57 PM, Chuck Lever wrote:
> 
> 
> Sent from my iPad
> 
> On Jun 5, 2011, at 11:43 AM, Steve Dickson <steved@redhat.com> wrote:
> 
>> With non-blocking connections, do not skip records when receiving
>> the streams since entire value messages can be ignored which
>> in cause the entire stream to become out of sync.
>>
>> For example, two mounts simultaneously send two unmaps
>> commands. The first one is read, then the second thrown
>> away due to skipping the record. Skipping this record
>> will cause XDR error later in processing of the stream.
>>
>> Signed-off-by: Steve Dickson <steved@redhat.com>
>> ---
>> src/svc_vc.c |    5 +++++
>> 1 files changed, 5 insertions(+), 0 deletions(-)
>>
>> diff --git a/src/svc_vc.c b/src/svc_vc.c
>> index aaaf2d7..15dac18 100644
>> --- a/src/svc_vc.c
>> +++ b/src/svc_vc.c
>> @@ -610,6 +610,11 @@ svc_vc_recv(xprt, msg)
>>    }
>>
>>    xdrs->x_op = XDR_DECODE;
>> +    /*
>> +     * No need skip records with nonblocking connections
>> +     */
>> +    if (cd->nonblock == FALSE)
>> +        (void)xdrrec_skiprecord(xdrs);
>>    (void)xdrrec_skiprecord(xdrs);
> 
> Do you want to delete the unconditional invocation of xdrrec_skiprecord() here?
Yes I do... a small cut/past error... good catch!

steved.
> 
>>    if (xdr_callmsg(xdrs, msg)) {
>>        cd->x_id = msg->rm_xid;
>> -- 
>> 1.7.4.4
>>
>>
>> ------------------------------------------------------------------------------
>> Simplify data backup and recovery for your virtual environment with vRanger.
>> Installation's a snap, and flexible recovery options mean your data is safe,
>> secure and there when you need it. Discover what all the cheering's about.
>> Get your free trial download today. 
>> http://p.sf.net/sfu/quest-dev2dev2 
>> _______________________________________________
>> Libtirpc-devel mailing list
>> Libtirpc-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/libtirpc-devel

      reply	other threads:[~2011-06-05 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05 15:43 [PATCH] Do not skip records with nonblocking connections Steve Dickson
2011-06-05 22:57 ` [Libtirpc-devel] " Chuck Lever
2011-06-05 23:51   ` Steve Dickson [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=4DEC1692.6070504@RedHat.com \
    --to=steved@redhat.com \
    --cc=chucklever@gmail.com \
    --cc=libtirpc-devel@lists.sourceforge.net \
    --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 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.