From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Fang TongHao <fangtonghao@sangfor.com.cn>,
thomas@monjalon.net
Cc: dev@dpdk.org, stable@dpdk.org, jia.guo@intel.com,
cunming.liang@intel.com, qi.z.zhang@intel.com,
jungle845943968@outlook.com, jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH v3] Fixes: ethdev: secondary process change shared memory
Date: Fri, 17 Jan 2020 17:58:15 +0000 [thread overview]
Message-ID: <c836d98a-01f3-3f13-e24f-26ea1148426e@intel.com> (raw)
In-Reply-To: <a854dc6d-d16c-6ac1-c080-42b91232a380@solarflare.com>
On 1/17/2020 8:33 AM, Andrew Rybchenko wrote:
> On 1/17/20 5:08 AM, Fang TongHao wrote:
>
> Summary does not comply with [1].
>
>> Fixes the secondary process changed shared memory
>> in "rte_eth_copy_pci_info" function.In that function
>> only primary can update the value of "eth_dev->data"
>> which shared by primary and secondary.
>
> Consider:
> Avoid overwriting device flags and other information in device
> data stored in shared memory when a secondary process
> probes PCI device.
>
> Fixes tag and CC to stable is required in accordance with [2].
>
>> Signed-off-by: Fang TongHao <fangtonghao@sangfor.com.cn>
>
> [1]
> https://doc.dpdk.org/guides/contributing/patches.html#commit-messages-subject-line
> [2]
> https://doc.dpdk.org/guides/contributing/patches.html#commit-messages-body
>
For sake of having the patch in -rc1, I have updated as suggested while merging,
commit log become as following:
ethdev: fix secondary process memory overwrite
Avoid overwriting device flags and other information in device
data stored in shared memory when a secondary process
probes PCI device.
Fixes: 494adb7f63f2 ("ethdev: add device fields from PCI layer")
Cc: stable@dpdk.org
Signed-off-by: Fang TongHao <fangtonghao@sangfor.com.cn>
Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
And I have added a not the the function comment as following:
* Copy pci device info to the Ethernet device data.
+ * Shared memory (eth_dev->data) only updated by primary process, so it is safe
+ * to call this function from both primary and secondary processes.
*
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-01-17 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 12:27 [dpdk-dev] [PATCH] ethdev: fix secondary process change share memory Fang TongHao
2020-01-10 7:30 ` Jeff Guo
2020-01-10 7:53 ` 方统浩50450
2020-01-13 5:03 ` [dpdk-dev] [PATCH v2] Fixes: ethdev: secondary process change shared memory Fang TongHao
2020-01-14 14:45 ` Ferruh Yigit
2020-01-15 6:49 ` 方统浩50450
2020-01-15 18:35 ` Ferruh Yigit
2020-01-15 20:43 ` Thomas Monjalon
2020-01-16 7:43 ` Andrew Rybchenko
2020-01-16 9:04 ` Ferruh Yigit
2020-01-16 11:35 ` 方统浩50450
2020-01-16 12:18 ` Ferruh Yigit
2020-01-17 2:11 ` 方统浩50450
2020-01-16 9:00 ` Ferruh Yigit
2020-01-17 2:08 ` [dpdk-dev] [PATCH v3] " Fang TongHao
2020-01-17 8:33 ` Andrew Rybchenko
2020-01-17 17:58 ` Ferruh Yigit [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=c836d98a-01f3-3f13-e24f-26ea1148426e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=cunming.liang@intel.com \
--cc=dev@dpdk.org \
--cc=fangtonghao@sangfor.com.cn \
--cc=jerinj@marvell.com \
--cc=jia.guo@intel.com \
--cc=jungle845943968@outlook.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).