From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: "dapengx.yu@intel.com" <dapengx.yu@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH 20.11 v2] net/iavf: fix multi-process shared data
Date: Sat, 27 Nov 2021 14:27:10 +0000 [thread overview]
Message-ID: <9d853a7339037eb0f6c4a39f12273e458bb5f88a.camel@nvidia.com> (raw)
In-Reply-To: <20211111054851.510128-1-dapengx.yu@intel.com>
On Thu, 2021-11-11 at 13:48 +0800, dapengx.yu@intel.com wrote:
> From: Dapeng Yu <dapengx.yu@intel.com>
>
> [ upstream commit 435d523112ccef6cb58edba3062ea05a2f6544fc ]
>
> When the iavf_adapter instance is not initialized completedly in the
> primary process, the secondary process accesses its "rte_eth_dev"
> member, it causes secondary process crash.
>
> This patch replaces eth_dev with eth_dev_data in iavf_adapter.
>
> Fixes: f978c1c9b3b5 ("net/iavf: add RSS hash parsing in AVX path")
> Fixes: 9c9aa0040344 ("net/iavf: add offload path for Rx AVX512 flex descriptor")
> Fixes: 63660ea3ee0b ("net/iavf: add RSS hash parsing in SSE path")
>
> Signed-off-by: Dapeng Yu <dapengx.yu@intel.com>
> ---
> V2:
> * Simplify parameters of iavf_request_queues
> * Clean commit log
> ---
Applied to 20.11.4 list, thanks!
prev parent reply other threads:[~2021-11-27 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 5:48 dapengx.yu
2021-11-27 14:27 ` Xueming(Steven) Li [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=9d853a7339037eb0f6c4a39f12273e458bb5f88a.camel@nvidia.com \
--to=xuemingl@nvidia.com \
--cc=dapengx.yu@intel.com \
--cc=stable@dpdk.org \
/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).