From: Chas Williams <3chas3@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, "Yigit, Ferruh" <ferruh.yigit@intel.com>,
chas3@att.com, "Zhaohui (zhaohui,
Polestar)" <zhaohui8@huawei.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [PATCH 2/2] net/bonding: fix oob access in "other" aggregator modes
Date: Sun, 24 Mar 2019 13:24:00 -0400 [thread overview]
Message-ID: <8eb07dc9-0640-66bd-22aa-e8518d449e97@gmail.com> (raw)
In-Reply-To: <CAJFAV8wn0VAu41ZriTfUpXs4jLXeLxQz3=rCCOhfrvhNYPc+kQ@mail.gmail.com>
On 3/24/19 1:11 PM, David Marchand wrote:
> On Sun, Mar 24, 2019 at 2:35 PM Chas Williams <3chas3@gmail.com
> <mailto:3chas3@gmail.com>> wrote:
>
> Have you ever experienced this problem in practice? I ask because I am
> considering some fixes that would limit the number of slaves to a more
> reasonable number (and reduce the over stack usage of the bonding
> driver
> in general).
>
>
> Not too hard to reproduce, the problem is not the number of slaves.
> With a default RTE_MAX_ETHPORTS at 32, any slave whose portid >= 8 would
> trigger an oob access.
Err... Well I have a lot of questions then about this whole thing. What
is max_index() doing?
mode_count_id = max_index(agg_count, slaves_count);
It's indexing up to slaves_count, which is likely to be somewhere around
2. agg_count() is indexed by the port id. It's likely agg_count was
intended to be indexed by the slave index and not the port id.
>
>
> Example:
> # git describe
> v19.02-294-gad2f555
>
> # gdb ./master/app/testpmd
> (gdb) b selection_logic
> (gdb) run -c 0x3 --no-pci --vdev net_ring0 --vdev net_ring1 --vdev
> net_ring2 --vdev net_ring3 --vdev net_ring4 --vdev net_ring5 --vdev
> net_ring6 --vdev net_ring7 --vdev net_ring8 --vdev net_ring9 --vdev
> net_bonding0,mode=4,slave=8,slave=9 -- -i --total-num-mbufs 2048
>
> Breakpoint 1, selection_logic (internals=0x17fe51980, slave_id=8) at
> /root/dpdk/drivers/net/bonding/rte_eth_bond_8023ad.c:670
> 670 uint16_t slaves_count, new_agg_id, i, j = 0;
> Missing separate debuginfos, use: debuginfo-install
> glibc-2.17-260.el7_6.3.x86_64 libgcc-4.8.5-36.el7.x86_64
> numactl-libs-2.0.9-7.el7.x86_64
> (gdb) n
> 672 uint64_t agg_bandwidth[8] = {0};
> (gdb)
> 673 uint64_t agg_count[8] = {0};
> (gdb)
> 674 uint16_t default_slave = 0;
> (gdb) p agg_bandwidth
> $1 = {0, 0, 0, 0, 0, 0, 0, 0}
> (gdb) p agg_count
> $2 = {0, 0, 0, 0, 0, 0, 0, 0}
> (gdb) n
> 678 slaves = internals->active_slaves;
> (gdb)
> 679 slaves_count = internals->active_slave_count;
> (gdb)
> 680 port = &bond_mode_8023ad_ports[slave_id];
> (gdb)
> 683 for (i = 0; i < slaves_count; ++i) {
> (gdb)
> 684 agg = &bond_mode_8023ad_ports[slaves[i]];
> (gdb)
> 686 if (agg->aggregator_port_id != slaves[i])
> (gdb)
> 689 agg_count[agg->aggregator_port_id] += 1;
> (gdb)
> 690 rte_eth_link_get_nowait(slaves[i], &link_info);
> (gdb) p agg_bandwidth
> $3 = {1, 0, 0, 0, 0, 0, 0, 0}
> (gdb) p agg_count
> $4 = {0, 0, 0, 0, 0, 0, 0, 0}
>
>
> --
> David Marchand
next prev parent reply other threads:[~2019-03-24 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 20:28 [PATCH 1/2] net/bonding: fix more incorrect slave id types David Marchand
2019-03-21 20:28 ` [PATCH 2/2] net/bonding: fix oob access in "other" aggregator modes David Marchand
2019-03-22 11:18 ` Maxime Coquelin
2019-03-24 13:35 ` Chas Williams
2019-03-24 17:11 ` David Marchand
2019-03-24 17:24 ` Chas Williams [this message]
2019-03-24 18:01 ` David Marchand
2019-09-30 13:49 ` [dpdk-dev] " Yigit, Ferruh
2019-03-22 11:18 ` [PATCH 1/2] net/bonding: fix more incorrect slave id types Maxime Coquelin
2019-09-30 13:49 ` [dpdk-dev] " Yigit, Ferruh
2019-03-24 13:28 ` Chas Williams
2019-03-24 17:13 ` David Marchand
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=8eb07dc9-0640-66bd-22aa-e8518d449e97@gmail.com \
--to=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--cc=zhaohui8@huawei.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 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.