From: Junxiao Bi <junxiao.bi@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: jlbec@evilplan.org, joseph.qi@huawei.com, mfasheh@suse.de,
stable@vger.kernel.org
Subject: Re: + revert-ocfs2-bump-up-o2cb-network-protocol-version.patch added to -mm tree
Date: Tue, 20 Sep 2016 08:46:06 +0800 [thread overview]
Message-ID: <f5af5cb7-3c5c-241e-6a78-5a8be4d8ff00@oracle.com> (raw)
In-Reply-To: <20160919115709.a644c5cad412c18324adff28@linux-foundation.org>
On 09/20/2016 02:57 AM, Andrew Morton wrote:
> On Sun, 18 Sep 2016 23:32:34 +0800 Junxiao Bi <junxiao.bi@oracle.com> wrote:
>
>> Hi Andrew,
>>
>> Please drop this patch, it had been merged by mainline.
>
> Confused. I'm not seeing this in minaline.
Sorry, my fault. Something wrong in my local repo. Now it is merged.
Thanks,
Junxiao.
>
>> Thanks,
>> Junxiao.
>>> ___ 2016___9___15____________6:45___akpm@linux-foundation.org _________
>>>
>>>
>>> The patch titled
>>> Subject: Revert "ocfs2: bump up o2cb network protocol version"
>>> has been added to the -mm tree. Its filename is
>>> revert-ocfs2-bump-up-o2cb-network-protocol-version.patch
>>>
>>> This patch should soon appear at
>>> http://ozlabs.org/~akpm/mmots/broken-out/revert-ocfs2-bump-up-o2cb-network-protocol-version.patch
>>> and later at
>>> http://ozlabs.org/~akpm/mmotm/broken-out/revert-ocfs2-bump-up-o2cb-network-protocol-version.patch
>>>
>>> Before you just go and hit "reply", please:
>>> a) Consider who else should be cc'ed
>>> b) Prefer to cc a suitable mailing list as well
>>> c) Ideally: find the original patch on the mailing list and do a
>>> reply-to-all to that, adding suitable additional cc's
>>>
>>> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>>>
>>> The -mm tree is included into linux-next and is updated
>>> there every 3-4 working days
>>>
>>> ------------------------------------------------------
>>> From: Junxiao Bi <junxiao.bi@oracle.com>
>>> Subject: Revert "ocfs2: bump up o2cb network protocol version"
>>>
>>> This reverts commit 38b52efd218bf ("ocfs2: bump up o2cb network
>>> protocol version").
>>>
>>> This commit made rolling upgrade fail. When one node is upgraded to new
>>> version with this commit, the remaining nodes will fail to establish
>>> connections to it, then the application like VMs on the remaining nodes
>>> can't be live migrated to the upgraded one. This will cause an outage.
>>> Since negotiate hb timeout behavior didn't change without this commit, so
>>> revert it.
>>>
>>> Fixes: 38b52efd218bf ("ocfs2: bump up o2cb network protocol version")
>>> Link: http://lkml.kernel.org/r/1471396924-10375-1-git-send-email-junxiao.bi@oracle.com
>>> Signed-off-by: Junxiao Bi <junxiao.bi@oracle.com>
>>> Cc: Mark Fasheh <mfasheh@suse.de>
>>> Cc: Joel Becker <jlbec@evilplan.org>
>>> Cc: Joseph Qi <joseph.qi@huawei.com>
>>> Cc: <stable@vger.kernel.org>
>>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>>> ---
>>>
>>> fs/ocfs2/cluster/tcp_internal.h | 5 +----
>>> 1 file changed, 1 insertion(+), 4 deletions(-)
>>>
>>> diff -puN fs/ocfs2/cluster/tcp_internal.h~revert-ocfs2-bump-up-o2cb-network-protocol-version fs/ocfs2/cluster/tcp_internal.h
>>> --- a/fs/ocfs2/cluster/tcp_internal.h~revert-ocfs2-bump-up-o2cb-network-protocol-version
>>> +++ a/fs/ocfs2/cluster/tcp_internal.h
>>> @@ -44,9 +44,6 @@
>>> * version here in tcp_internal.h should not need to be bumped for
>>> * filesystem locking changes.
>>> *
>>> - * New in version 12
>>> - * - Negotiate hb timeout when storage is down.
>>> - *
>>> * New in version 11
>>> * - Negotiation of filesystem locking in the dlm join.
>>> *
>>> @@ -78,7 +75,7 @@
>>> * - full 64 bit i_size in the metadata lock lvbs
>>> * - introduction of "rw" lock and pushing meta/data locking down
>>> */
>>> -#define O2NET_PROTOCOL_VERSION 12ULL
>>> +#define O2NET_PROTOCOL_VERSION 11ULL
>>> struct o2net_handshake {
>>> __be64 protocol_version;
>>> __be64 connector_id;
>>> _
>>>
>>> Patches currently in -mm which might be from junxiao.bi@oracle.com are
>>>
>>> ocfs2-fix-trans-extend-while-flush-truncate-log.patch
>>> ocfs2-fix-trans-extend-while-free-cached-blocks.patch
>>> revert-ocfs2-bump-up-o2cb-network-protocol-version.patch
>>>
>>
prev parent reply other threads:[~2016-09-20 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 22:45 + revert-ocfs2-bump-up-o2cb-network-protocol-version.patch added to -mm tree akpm
2016-09-18 15:32 ` Junxiao Bi
2016-09-19 18:57 ` Andrew Morton
2016-09-20 0:46 ` Junxiao Bi [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=f5af5cb7-3c5c-241e-6a78-5a8be4d8ff00@oracle.com \
--to=junxiao.bi@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@huawei.com \
--cc=mfasheh@suse.de \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).