From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhang, Yuying" <yuying.zhang@intel.com>,
"Zhang, Ke1X" <ke1x.zhang@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Xing, Beilei" <beilei.xing@intel.com>,
"ferruh.yigit@xilinx.com" <ferruh.yigit@xilinx.com>,
"Zhou, YidingX" <yidingx.zhou@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v4] net/i40e: fix the issue caused by PF and VF release order
Date: Mon, 8 Aug 2022 00:06:21 +0000 [thread overview]
Message-ID: <DM4PR11MB5994A581A01D69C4BA8C5095D7639@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM6PR11MB3516F21EB26D6B39F196798E8E9D9@DM6PR11MB3516.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Zhang, Yuying <yuying.zhang@intel.com>
> Sent: Tuesday, August 2, 2022 10:16 AM
> To: Zhang, Ke1X <ke1x.zhang@intel.com>; thomas@monjalon.net; Xing,
> Beilei <beilei.xing@intel.com>; ferruh.yigit@xilinx.com; Zhou, YidingX
> <yidingx.zhou@intel.com>; dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: RE: [PATCH v4] net/i40e: fix the issue caused by PF and VF release
> order
>
> Hi Ke,
>
> Please update commit log.
> LGTM.
>
> > -----Original Message-----
> > From: Zhang, Ke1X <ke1x.zhang@intel.com>
> > Sent: Friday, July 15, 2022 5:04 PM
> > To: thomas@monjalon.net; Zhang, Yuying <yuying.zhang@intel.com>; Xing,
> > Beilei <beilei.xing@intel.com>; ferruh.yigit@xilinx.com; Zhou, YidingX
> > <yidingx.zhou@intel.com>; dev@dpdk.org
> > Cc: Zhang, Ke1X <ke1x.zhang@intel.com>; stable@dpdk.org
> > Subject: [PATCH v4] net/i40e: fix the issue caused by PF and VF
> > release order
> >
> > A segmentation fault occurs when testpmd exit.
> >
> > This is due to fetching the device name from PF, PF is freed firstly
> > and then VF representor is called later.
> >
> > This commit fixes the bug by fetching the device name from VF
> > representor not PF.
>
> instead of PF
>
> >
> > Fixes: e391a7b7f815 ("net/i40e: fix multi-process shared data")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Ke Zhang <ke1x.zhang@intel.com>
> Acked-by: Yuying Zhang <yuying.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2022-08-08 0:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 7:18 [PATCH] app/testpmd: fix quit testpmd with vfs and pf Ke Zhang
2022-03-28 10:06 ` Singh, Aman Deep
2022-03-31 8:28 ` Singh, Aman Deep
2022-06-17 18:53 ` Ferruh Yigit
2022-06-21 9:03 ` [PATCH v2] " Ke Zhang
2022-06-21 9:20 ` Ferruh Yigit
2022-06-21 9:24 ` Ke Zhang
2022-06-21 10:43 ` Ferruh Yigit
2022-06-22 21:31 ` Thomas Monjalon
2022-06-23 6:41 ` Thomas Monjalon
2022-07-13 7:11 ` [PATCH v3] " Ke Zhang
2022-07-13 9:15 ` Thomas Monjalon
2022-07-15 9:03 ` [PATCH v4] net/i40e: fix the issue caused by PF and VF release order Ke Zhang
2022-08-02 2:16 ` Zhang, Yuying
2022-08-08 0:06 ` Zhang, Qi Z [this message]
2022-08-08 0:30 ` Zhang, Qi Z
2022-08-04 9:50 ` [PATCH v5] " Ke Zhang
2022-08-08 0:30 ` Zhang, Qi Z
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=DM4PR11MB5994A581A01D69C4BA8C5095D7639@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=ke1x.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yidingx.zhou@intel.com \
--cc=yuying.zhang@intel.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).