From: Greg KH <gregkh@linuxfoundation.org>
To: Timo Rothenpieler <timo@rothenpieler.org>
Cc: stable@vger.kernel.org, Eran Ben Elisha <eranbe@nvidia.com>,
Jack Wang <xjtuwjp@gmail.com>, Saeed Mahameed <saeedm@nvidia.com>,
jgg@ziepe.ca
Subject: Re: Backport missing mlx5 fixes after 50b2412b7e7
Date: Fri, 20 Nov 2020 09:37:54 +0100 [thread overview]
Message-ID: <X7eAYoNA2RktjH5B@kroah.com> (raw)
In-Reply-To: <f1c78926-b95b-c4b0-c323-c7a5ca1c8856@rothenpieler.org>
On Wed, Nov 18, 2020 at 07:28:30PM +0100, Timo Rothenpieler wrote:
> Hi,
>
> After 50b2412b7e7862c5af0cbf4b10d93bc5c712d021 was backported to stable
> branches (I only tested 5.4), some serious issues started to arrise.
>
> According to linux-rdma, the following two patches that need to go along
> with 50b2412b7e are missing:
>
> > 1. 1d5558b1f0de net/mlx5: poll cmd EQ in case of command timeout
> > 2. 410bd754cd73 net/mlx5: Add retry mechanism to the command entry ...
>
> I managed to apply those mostly cleanly after also applying two
> dependencies.
> So the complete list of needed commits for 5.4 is:
>
> 1. 3ed879965cc4 net/mlx5: Use async EQ setup cleanup helpers ...
> 2. 1d5558b1f0de net/mlx5: poll cmd EQ in case of command timeout
> 3. d43b7007dbd1 net/mlx5: Fix a race when moving command ...
> 4. 410bd754cd73 net/mlx5: Add retry mechanism to the command entry ...
>
> With those 4 commits applied, the issue is fixed.
> For reference, that's the output I get with 5.4.77:
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2020-11-20 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 18:28 Backport missing mlx5 fixes after 50b2412b7e7 Timo Rothenpieler
2020-11-20 6:18 ` Jack Wang
2020-11-22 17:48 ` Sasha Levin
2020-11-20 8:37 ` Greg KH [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=X7eAYoNA2RktjH5B@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=eranbe@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=saeedm@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=timo@rothenpieler.org \
--cc=xjtuwjp@gmail.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