patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: "Dey, Souvik" <sodey@rbbn.com>
Cc: viacheslavo@nvidia.com, shahafs@nvidia.com, matan@nvidia.com,
	 rasland@nvidia.com, dpdk stable <stable@dpdk.org>,
	dev <dev@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 19.11] net/mlx5: fix storing the synched MAC to internal table
Date: Mon, 15 Feb 2021 17:41:41 +0100	[thread overview]
Message-ID: <CAATJJ0J9R1onJfTgiGYPzwqod86Yy6mCCdsxvdWi=M8md1dSfg@mail.gmail.com> (raw)
In-Reply-To: <CAATJJ0KHo+2y-rd1+7f1yaALNmSUiJmUP0Z2OtY1VBjKu08z5A@mail.gmail.com>

On Mon, Feb 15, 2021 at 1:21 PM Christian Ehrhardt
<christian.ehrhardt@canonical.com> wrote:
>
> On Fri, Feb 12, 2021 at 4:10 PM Dey, Souvik <sodey@rbbn.com> wrote:
> >
> > From: Souvik Dey <sodey@rbbn.com>
> >
> > [ upstream commit 493f0bb51c1144eedcff2bba199cab1b64ff9fd0 ]
>
> Thanks, added
>
> >
> > As the internal MAC table is divided into Unicast and Multicast address
> > sections, we should check the type of synched MAC address before storing
> > it to the internal table. Currently the check is not done, and the
> > synched MAC of 33:33:00:00:00:01 gets stored in the unicast section
> > (mostly index 1) causing all subsequent mlx5_set_mc_addr_list()
> > to fail with error -EADDRINUSE, as the mac_list contains the MAC
> > 33:33:00:00:00:01. This denies adding of any new multicast address to
> > the internal list and also fails to add the MAC address to the device
> > in case of SR-IOV VF.
> >
> > Fixes: f22442cb5d42 ("net/mlx5: reduce Netlink commands dependencies")
> > Fixes: ccdcba53a3f4 ("net/mlx5: use Netlink to add/remove MAC addresses")
> >
> > Signed-off-by: Souvik Dey <sodey@rbbn.com>
> > ---
> >  drivers/net/mlx5/mlx5_nl.c | 21 ++++++++++++++++-----
> >  1 file changed, 16 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/net/mlx5/mlx5_nl.c b/drivers/net/mlx5/mlx5_nl.c
> > index 64580b9..add756d 100644
> > --- a/drivers/net/mlx5/mlx5_nl.c
> > +++ b/drivers/net/mlx5/mlx5_nl.c
> > @@ -678,11 +678,22 @@ mlx5_nl_mac_addr_sync(struct rte_eth_dev *dev)
> >                                 break;
> >                 if (j != MLX5_MAX_MAC_ADDRESSES)
> >                         continue;
> > -               /* Find the first entry available. */
> > -               for (j = 0; j != MLX5_MAX_MAC_ADDRESSES; ++j) {
> > -                       if (rte_is_zero_ether_addr(&dev->data->mac_addrs[j])) {
> > -                               dev->data->mac_addrs[j] = macs[i];


When built this fails, thereby for now I've dequeued this from 19.11.7

[  708s] ../drivers/net/mlx5/mlx5_nl.c: In function ‘mlx5_nl_mac_addr_sync’:
[  708s] ../drivers/net/mlx5/mlx5_nl.c:685:33: error: ‘mac_addrs’
undeclared (first use in this function); did you mean ‘vec_adds’?
[  708s]      if (rte_is_zero_ether_addr(&mac_addrs[j])) {
[  708s]                                  ^~~~~~~~~
[  708s]                                  vec_adds
[  708s] ../drivers/net/mlx5/mlx5_nl.c:685:33: note: each undeclared
identifier is reported only once for each function it appears in
[  708s] ninja: build stopped: subcommand failed.

If you have a chance to refresh your backport with the 19.11 codebase
in mind that would be great.
Looking for an updated backport and thanks in advance.

> > -                               break;
> > +               if (rte_is_multicast_ether_addr(&macs[i])) {
> > +                       /* Find the first entry available. */
> > +                       for (j = MLX5_MAX_UC_MAC_ADDRESSES;
> > +                            j != MLX5_MAX_MAC_ADDRESSES; ++j) {
> > +                               if (rte_is_zero_ether_addr(&mac_addrs[j])) {
> > +                                       mac_addrs[j] = macs[i];
> > +                                       break;
> > +                               }
> > +                       }
> > +               } else {
> > +                       /* Find the first entry available. */
> > +                       for (j = 0; j != MLX5_MAX_UC_MAC_ADDRESSES; ++j) {
> > +                               if (rte_is_zero_ether_addr(&mac_addrs[j])) {
> > +                                       mac_addrs[j] = macs[i];
> > +                                       break;
> > +                               }
> >                         }
> >                 }
> >         }
> > --
> > 2.9.3.windows.1
> >
> >
> > Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
>
>
>
> --
> Christian Ehrhardt
> Staff Engineer, Ubuntu Server
> Canonical Ltd



-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

  reply	other threads:[~2021-02-15 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 15:10 Dey, Souvik
2021-02-15 12:21 ` Christian Ehrhardt
2021-02-15 16:41   ` Christian Ehrhardt [this message]
2021-02-17 21:03 ` [dpdk-stable] [PATCH 19.11 v2] " Dey, Souvik

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='CAATJJ0J9R1onJfTgiGYPzwqod86Yy6mCCdsxvdWi=M8md1dSfg@mail.gmail.com' \
    --to=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=sodey@rbbn.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@nvidia.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).