From: Vitaliy Gusev <gusev.vitaliy@nexenta.com>
To: Andy Adamson <androsadamson@gmail.com>
Cc: "Adamson, Andy" <William.Adamson@netapp.com>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs41: Initialize slot->seq_nr at nfs4_init_slot_table()
Date: Wed, 15 Feb 2012 19:27:04 +0400 [thread overview]
Message-ID: <4F3BCEC8.6050509@nexenta.com> (raw)
In-Reply-To: <CAHVgHyXaAQvngPMrv+NaOKvKauHaqWJJbjqciJCOtJwYuSKVow@mail.gmail.com>
On 02/15/2012 07:16 PM, Andy Adamson wrote:
>>> No, commit aacd5537270a752fe12a9914a207284fc2341c6d initializes and resets
>>> the slot tables with the ivalue
>>> which is 1 for the forechannel and 0 for the back channel, just as in 3.2.
>>
>>
>>
>> nfs4_init_slot_table() doesn't use ivalue at all.
>
> Yep - that is the bug - which is in v2.6.39, and v3.2 ....
This bug was introduced by commit aacd5537270
next prev parent reply other threads:[~2012-02-15 15:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 21:48 [PATCH] nfs41: Initialize slot->seq_nr at nfs4_init_slot_table() Vitaliy Gusev
2012-02-14 22:46 ` Myklebust, Trond
2012-02-15 0:34 ` Vitaliy Gusev
2012-02-15 0:43 ` Myklebust, Trond
2012-02-15 0:53 ` J. Bruce Fields
2012-02-15 1:50 ` Myklebust, Trond
2012-02-15 2:30 ` Myklebust, Trond
2012-02-15 14:11 ` Vitaliy Gusev
2012-02-15 15:07 ` Adamson, Andy
2012-02-15 15:46 ` Myklebust, Trond
2012-02-15 16:06 ` Andy Adamson
2012-02-15 18:37 ` Myklebust, Trond
2012-02-15 18:45 ` Adamson, Andy
2012-02-15 15:01 ` Adamson, Andy
2012-02-15 15:06 ` Vitaliy Gusev
2012-02-15 15:16 ` Andy Adamson
2012-02-15 15:27 ` Vitaliy Gusev [this message]
2012-02-15 15:29 ` Myklebust, Trond
2012-02-15 15:45 ` Andy Adamson
2012-02-15 15:52 ` J. Bruce Fields
2012-02-15 15:15 ` Andy Adamson
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=4F3BCEC8.6050509@nexenta.com \
--to=gusev.vitaliy@nexenta.com \
--cc=Trond.Myklebust@netapp.com \
--cc=William.Adamson@netapp.com \
--cc=androsadamson@gmail.com \
--cc=bfields@fieldses.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 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.