From: "Yuan, DukaiX" <dukaix.yuan@intel.com>
To: Ivan Malov <ivan.malov@oktetlabs.ru>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Jiang, YuX" <yux.jiang@intel.com>, Chas Williams <chas3@att.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [PATCH] net/bonding: fix device configure reentrancy
Date: Wed, 2 Nov 2022 03:35:50 +0000 [thread overview]
Message-ID: <CH2PR11MB44877386DF5EA5B78BAE7B3AE8399@CH2PR11MB4487.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221101161853.2702425-1-ivan.malov@oktetlabs.ru>
-----Original Message-----
From: Ivan Malov <ivan.malov@oktetlabs.ru>
Sent: 2022年11月2日 0:19
To: dev@dpdk.org
Cc: Jiang, YuX <yux.jiang@intel.com>; Chas Williams <chas3@att.com>; Min Hu (Connor) <humin29@huawei.com>; Burakov, Anatoly <anatoly.burakov@intel.com>; stable@dpdk.org; Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: [PATCH] net/bonding: fix device configure reentrancy
As per report [1], the previous patch for device configure code apparently overlooks the corner case of manually adding back-end devices to the bond using testpmd CLI. The problem is in removing back-end ports on re-configure instead of just stopping them. Fix that.
Fixes: 339f1ba51353 ("net/bonding: make configure method re-entrant")
Cc: stable@dpdk.org
[1] https://bugs.dpdk.org/show_bug.cgi?id=1119
Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
---
Tested-by: Dukai Yuan<dukaix.yuan@intel.com>
next prev parent reply other threads:[~2022-11-02 3:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 16:18 Ivan Malov
2022-11-01 19:32 ` Stephen Hemminger
2022-11-06 9:35 ` Andrew Rybchenko
2022-11-02 3:35 ` Yuan, DukaiX [this message]
2022-11-06 9:37 ` Andrew Rybchenko
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=CH2PR11MB44877386DF5EA5B78BAE7B3AE8399@CH2PR11MB4487.namprd11.prod.outlook.com \
--to=dukaix.yuan@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=ivan.malov@oktetlabs.ru \
--cc=stable@dpdk.org \
--cc=yux.jiang@intel.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).