From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: "koncept1@gmail.com" <koncept1@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ben.magistro@trinitycyber.com" <ben.magistro@trinitycyber.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable][20.11] [PATCH v4] net/i40e: fix i40evf device initialization
Date: Sat, 27 Nov 2021 13:34:33 +0000 [thread overview]
Message-ID: <1a649a148356c33b2f964c95d3e8f14b8cc97969.camel@nvidia.com> (raw)
In-Reply-To: <20211108155449.31323-1-koncept1@gmail.com>
On Mon, 2021-11-08 at 15:54 +0000, Ben Magistro wrote:
> The i40evf driver is not initializing the eth_dev attribute which
> can result in a nullptr dereference. Changes were modeled after the
> iavf_dev_init() per suggestion from the mailing list[1] and
> i40evf_init_vf().
>
> [1] https://mails.dpdk.org/archives/dev/2021-August/217251.html
>
> Rebased on v20.11.3.
>
> Fixes: 4861cde46116 ("i40e: new poll mode driver")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ben Magistro <koncept1@gmail.com>
> ---
Hi Ben,
Applied to 20.11.4 list, thanks!
Best Regards,
Xueming Li
prev parent reply other threads:[~2021-11-27 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210825194526.14987-1-koncept1@gmail.com>
[not found] ` <94f93212-6432-710b-1135-638e359741da@intel.com>
[not found] ` <11dd4ae3-0396-b237-7f2b-1484f07bb637@redhat.com>
[not found] ` <DM4PR12MB5373F257EB40412DB8614815A1C89@DM4PR12MB5373.namprd12.prod.outlook.com>
[not found] ` <9527de1a-30ac-9bc9-ad11-14fbcd5207a1@intel.com>
[not found] ` <DM4PR12MB537374EE140EFF70B2ADD3DCA1CE9@DM4PR12MB5373.namprd12.prod.outlook.com>
2021-09-14 2:52 ` [dpdk-stable] [dpdk-dev] [PATCH] driver: " Ben Magistro
2021-09-17 14:44 ` [dpdk-stable] [PATCH v2, 20.11] net/i40e: fix " Ben Magistro
2021-09-28 21:23 ` Ben Magistro
2021-10-12 14:17 ` [dpdk-stable] [PATCH v3] " Ben Magistro
2021-11-08 11:21 ` [dpdk-stable] [dpdk-dev] " Xueming(Steven) Li
2021-11-08 15:54 ` [dpdk-stable] [PATCH v4] " Ben Magistro
2021-11-27 13:34 ` 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=1a649a148356c33b2f964c95d3e8f14b8cc97969.camel@nvidia.com \
--to=xuemingl@nvidia.com \
--cc=ben.magistro@trinitycyber.com \
--cc=dev@dpdk.org \
--cc=koncept1@gmail.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).