From: Thomas Glanzmann <thomas@glanzmann•de>
To: Ding Tianhong <dingtianhong@huawei•com>
Cc: fubar@us•ibm.com, vfalico@redhat•com, andy@greyhouse•net,
cwang@twopensource•com, jiri@resnulli•us, eric.dumazet@gmail•com,
sfeldma@cumulusnetworks•com, davem@davemloft•net,
netdev@vger•kernel.org
Subject: Re: [PATCH net v2 0/2] Fix RTNL: assertion failed at net/core/rtnetlink.c
Date: Wed, 19 Feb 2014 11:52:00 +0100 [thread overview]
Message-ID: <20140219105200.GA18298@glanzmann.de> (raw)
In-Reply-To: <1392800711-19264-1-git-send-email-dingtianhong@huawei.com>
Hello Ding,
> v1->v2: Add new micro to indicate that the notification should be send
> later, not never.
> And add a new patch to fix the same problem for ARP mode.
> Ding Tianhong (2):
> bonding: Fix RTNL: assertion failed at net/core/rtnetlink.c for
> 802.3ad mode
> bonding: Fix RTNL: assertion failed at net/core/rtnetlink.c for ab
> arp monitor
the patch did not apply cleanly for me, so I manually merged it.
The resulting patch is here:
(node-62) [~/work/linux-2.6] git diff | pbot
http://pbot.rmdir.de/TDMvhGB775BVPpKvm6NOXg
Find the results here:
(node-62) [~] dmesg | pbot
http://pbot.rmdir.de/nogPmqfGRxxk9zMNBlr0QQ
(node-62) [~] pbot /proc/net/bonding/bond0
http://pbot.rmdir.de/zNSSqmjSI0o1Qvt6DrSEQw
(node-62) [~] pbot /proc/net/bonding/bond1
http://pbot.rmdir.de/CoI00Rguie2P-kOQytOM9w
Tested-by: Thomas Glanzmann <thomas@glanzmann•de>
Cheers,
Thomas
prev parent reply other threads:[~2014-02-19 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 9:05 [PATCH net v2 0/2] Fix RTNL: assertion failed at net/core/rtnetlink.c Ding Tianhong
2014-02-19 9:05 ` [PATCH net v2 1/2] bonding: Fix RTNL: assertion failed at net/core/rtnetlink.c for 802.3ad mode Ding Tianhong
2014-02-25 22:32 ` David Miller
2014-02-26 1:47 ` Ding Tianhong
2014-02-19 9:05 ` [PATCH net v2 2/2] bonding: Fix RTNL: assertion failed at net/core/rtnetlink.c for ab arp monitor Ding Tianhong
2014-02-25 22:34 ` David Miller
2014-02-19 10:52 ` Thomas Glanzmann [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=20140219105200.GA18298@glanzmann.de \
--to=thomas@glanzmann$(echo .)de \
--cc=andy@greyhouse$(echo .)net \
--cc=cwang@twopensource$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dingtianhong@huawei$(echo .)com \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=fubar@us$(echo .)ibm.com \
--cc=jiri@resnulli$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfeldma@cumulusnetworks$(echo .)com \
--cc=vfalico@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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