From: Luca Boccassi <bluca@debian.org>
To: "Yang, Ming 1. (NSB - CN/Hangzhou)" <ming.1.yang@nokia-sbell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "Zizka, Jan (Nokia - CZ/Prague)" <jan.zizka@nokia.com>,
"Xu,
Meng-Maggie (NSB - CN/Hangzhou)" <meng-maggie.xu@nokia-sbell.com>
Subject: Re: [dpdk-stable] [PATCH 20.11] Coverity issue: When IAVF driver used, some operation such as setting mtu will cause coredump if there is secondary process. Bugzilla ID: NA Fixes: Because secondary process wrongly modify shared data of rte_eth_dev. After iavf_dev_stop exec
Date: Tue, 07 Sep 2021 11:35:01 +0100 [thread overview]
Message-ID: <61ceed4701c22917c5cd33fde983d6dfb05685ff.camel@debian.org> (raw)
In-Reply-To: <fb9065e021eb47b598a5cf7cee96c37a@nokia-sbell.com>
On Fri, 2021-08-27 at 10:33 +0000, Yang, Ming 1. (NSB - CN/Hangzhou)
wrote:
> Hi DPDK maintainer,
>
> We want to upstream our dpdk patch for fixing bug. But it seems that "git send-email" still can't be work. Can you review and apply this patch to branch 20.11 of git repository dpdk_stable.
>
> ------------------------------------------------------------------------------------------------------------------------------
> Coverity issue: When IAVF driver used, some operation such as setting mtu will cause coredump if there is secondary process.
> Bugzilla ID: NA
> Fixes: Because secondary process wrongly modify shared data of rte_eth_dev. After iavf_dev_stop execute in primary process, rxq->ops->release_mbufs may be NULL point. Fix prevent secondary process to modify these shared data.
> Cc: stable@dpdk.org<mailto:stable@dpdk.org>
>
> Brs,
> Yang Ming
>
Hi,
I assume you added the patch as an attachment - that will not work,
attachments are not allowed on this mailing list. There was no patch in
your mail.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2021-09-07 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 10:33 Yang, Ming 1. (NSB - CN/Hangzhou)
2021-09-07 10:35 ` Luca Boccassi [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=61ceed4701c22917c5cd33fde983d6dfb05685ff.camel@debian.org \
--to=bluca@debian.org \
--cc=jan.zizka@nokia.com \
--cc=meng-maggie.xu@nokia-sbell.com \
--cc=ming.1.yang@nokia-sbell.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).