From: Luca Boccassi <bluca@debian.org>
To: Viacheslav Ovsiienko <viacheslavo@mellanox.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 19.11 v2] net/mlx5: fix last completed built descriptor
Date: Thu, 27 Feb 2020 13:13:54 +0000 [thread overview]
Message-ID: <6abeb72992b4a471765c7b095c02dc3a0f5bb26a.camel@debian.org> (raw)
In-Reply-To: <1582807239-17462-1-git-send-email-viacheslavo@mellanox.com>
On Thu, 2020-02-27 at 12:40 +0000, Viacheslav Ovsiienko wrote:
> The routine sending packets with Multi-Packet Write method assigns
> the wqe_last variable with transmit descriptor (WQE - work queue
> entry)
> being built. If send queue is close to full state, the WQE has no
> data
> yet (trying to put the first packet) and there is no enough space
> in descriptor for the next packet the WQE is discarded and the stored
> wqe_last value becomes invalid - points to the discarded WQE.
>
> The mlx5_tx_burst_request_completion() routine might set the
> completion
> request flags in the WQE pointed by wqe_last, it is safe, but the
> next
> mlx5_tx_burst call uses the WQE as the first free one and request
> completion flags might be overwritten and completion request will be
> lost causing the transmit datapath malfunction.
>
> Fixes: aa7c60a80997 ("net/mlx5: move Tx complete request routine")
> Cc:
> stable@dpdk.org
>
>
> Signed-off-by: Viacheslav Ovsiienko <
> viacheslavo@mellanox.com
> >
> Acked-by: Matan Azrad <
> matan@mellanox.com
> >
> ---
> drivers/net/mlx5/mlx5_rxtx.c | 51 +++++++++++++++++++++++++++-------
> ----------
> 1 file changed, 31 insertions(+), 20 deletions(-)
Thanks, applied.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2020-02-27 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 12:40 Viacheslav Ovsiienko
2020-02-27 13:13 ` Luca Boccassi [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=6abeb72992b4a471765c7b095c02dc3a0f5bb26a.camel@debian.org \
--to=bluca@debian.org \
--cc=stable@dpdk.org \
--cc=viacheslavo@mellanox.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).