From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Ben Magistro <koncept1@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>,
Beilei Xing <beilei.xing@intel.com>,
Luca Boccassi <bluca@debian.org>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: "ben.magistro@trinitycyber.com" <ben.magistro@trinitycyber.com>,
"stefan.baranoff@trinitycyber.com"
<stefan.baranoff@trinitycyber.com>,
Qi Zhang <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] driver: i40evf device initialization
Date: Fri, 27 Aug 2021 06:28:49 +0000 [thread overview]
Message-ID: <DM4PR12MB5373F257EB40412DB8614815A1C89@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <11dd4ae3-0396-b237-7f2b-1484f07bb637@redhat.com>
> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Thursday, August 26, 2021 6:46 PM
> To: Ferruh Yigit <ferruh.yigit@intel.com>; Ben Magistro <koncept1@gmail.com>; dev@dpdk.org; Beilei Xing <beilei.xing@intel.com>;
> Luca Boccassi <bluca@debian.org>; Christian Ehrhardt <christian.ehrhardt@canonical.com>; Xueming(Steven) Li
> <xuemingl@nvidia.com>
> Cc: ben.magistro@trinitycyber.com; stefan.baranoff@trinitycyber.com; Qi Zhang <qi.z.zhang@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] driver: i40evf device initialization
>
> + Christian and Xueming
>
> On 26/08/2021 11:25, Ferruh Yigit wrote:
> > On 8/25/2021 8:45 PM, 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].
> >>
> >> [1] https://mails.dpdk.org/archives/dev/2021-August/217251.html
> >>
> >> Signed-off-by: Ben Magistro <koncept1@gmail.com>
> >
> > i40evf will be removed in this release. But I guess it helps for
> > stable releases to first merge the fixes and later removed it, not sure.
> >
> > @Luca, @Kevin, do you prefer this patch directly to stable repos, or
> > through the main repo?
>
> I'll leave to Luca/Xueming and Christian to say if they have a preference, but I'd guess either way is fine from stable view once it has
> fixes/stable tags or LTS patch prefix (it doesn't have any of these at present).
Yes, any option will make it being noticed by LTS maintainer:
1. patches accepted by main with "fix" in subject
2. patches accepted by main with "cc: stable@dpdk.org" in commit message
3. patches backported to LTS, sent to stable maillist with LTS prefix, for example "[20.11]"
>
> > i40evf won't be tested in the main anyway, since it would be removed
> > before -rc1 testing, so it looks like there won't be any difference from testing point of view.
> >
> >
> >> ---
> >> drivers/net/i40e/i40e_ethdev_vf.c | 8 ++++++--
> >> 1 file changed, 6 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/net/i40e/i40e_ethdev_vf.c
> >> b/drivers/net/i40e/i40e_ethdev_vf.c
> >> index 0cfe13b7b2..ccdce9a16a 100644
> >> --- a/drivers/net/i40e/i40e_ethdev_vf.c
> >> +++ b/drivers/net/i40e/i40e_ethdev_vf.c
> >> @@ -1564,8 +1564,9 @@ i40evf_dev_alarm_handler(void *param) static
> >> int i40evf_dev_init(struct rte_eth_dev *eth_dev) {
> >> - struct i40e_hw *hw
> >> - = I40E_DEV_PRIVATE_TO_HW(eth_dev->data->dev_private);
> >> + struct i40e_adapter *adapter =
> >> + I40E_DEV_PRIVATE_TO_ADAPTER(eth_dev->data->dev_private);
> >> + struct i40e_hw *hw = I40E_DEV_PRIVATE_TO_HW(adapter);
> >> struct rte_pci_device *pci_dev = RTE_ETH_DEV_TO_PCI(eth_dev);
> >>
> >> PMD_INIT_FUNC_TRACE();
> >> @@ -1596,11 +1597,14 @@ i40evf_dev_init(struct rte_eth_dev *eth_dev)
> >> hw->device_id = pci_dev->id.device_id;
> >> hw->subsystem_vendor_id = pci_dev->id.subsystem_vendor_id;
> >> hw->subsystem_device_id = pci_dev->id.subsystem_device_id;
> >> + hw->bus.bus_id = pci_dev->addr.bus;
> >> hw->bus.device = pci_dev->addr.devid;
> >> hw->bus.func = pci_dev->addr.function;
> >> hw->hw_addr = (void *)pci_dev->mem_resource[0].addr;
> >> hw->adapter_stopped = 1;
> >> hw->adapter_closed = 0;
> >> + hw->back = I40E_DEV_PRIVATE_TO_ADAPTER(eth_dev->data->dev_private);
> >> + adapter->eth_dev = eth_dev;
> >>
> >> if(i40evf_init_vf(eth_dev) != 0) {
> >> PMD_INIT_LOG(ERR, "Init vf failed");
> >>
> >
next prev parent reply other threads:[~2021-08-27 6:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 19:45 Ben Magistro
2021-08-26 10:25 ` Ferruh Yigit
2021-08-26 10:46 ` Kevin Traynor
2021-08-27 6:28 ` Xueming(Steven) Li [this message]
2021-08-30 9:43 ` Ferruh Yigit
2021-09-02 12:37 ` Xueming(Steven) Li
2021-09-14 2:52 ` Ben Magistro
2021-10-13 13:21 ` Ben Magistro
2021-10-15 11:10 ` Xueming(Steven) Li
2021-09-28 21:23 ` [dpdk-dev] [PATCH v2, 20.11] net/i40e: fix " Ben Magistro
2021-10-12 14:17 ` [dpdk-dev] [PATCH v3] " Ben Magistro
2021-11-08 11:21 ` Xueming(Steven) Li
2021-11-08 15:54 ` [dpdk-dev] [PATCH v4] " Ben Magistro
2021-11-27 13:34 ` [dpdk-stable][20.11] " Xueming(Steven) Li
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=DM4PR12MB5373F257EB40412DB8614815A1C89@DM4PR12MB5373.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=beilei.xing@intel.com \
--cc=ben.magistro@trinitycyber.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=koncept1@gmail.com \
--cc=ktraynor@redhat.com \
--cc=qi.z.zhang@intel.com \
--cc=stefan.baranoff@trinitycyber.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).