From: wangyunjian <wangyunjian@huawei.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Raslan Darawsheh <rasland@nvidia.com>
Cc: Matan Azrad <matan@nvidia.com>,
Michael Baum <michaelba@nvidia.com>,
dingxiaoxiong <dingxiaoxiong@huawei.com>,
xudingke <xudingke@huawei.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [dpdk-dev] [PATCH 1/1] net/mlx5: fix stack buffer overflow of hrxq's rss_key
Date: Mon, 20 Jun 2022 05:59:03 +0000 [thread overview]
Message-ID: <3ce0eb9e4a8a46a4ad230715d9ec1878@huawei.com> (raw)
In-Reply-To: <DM6PR12MB3753BDBFDC512FB1B691F9C5DFB09@DM6PR12MB3753.namprd12.prod.outlook.com>
Just found by sanitizer, thanks.
Yunjian
-----Original Message-----
From: Slava Ovsiienko [mailto:viacheslavo@nvidia.com]
Sent: Monday, June 20, 2022 1:16 PM
To: wangyunjian <wangyunjian@huawei.com>; dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
Cc: Matan Azrad <matan@nvidia.com>; Michael Baum <michaelba@nvidia.com>; dingxiaoxiong <dingxiaoxiong@huawei.com>; xudingke <xudingke@huawei.com>; stable@dpdk.org
Subject: RE: [dpdk-dev] [PATCH 1/1] net/mlx5: fix stack buffer overflow of hrxq's rss_key
Hi, Yunjian
My sincere apologies for the review delay.
I think patch is OK, thank you for finding this.
Just of curiosity - did you observe a real crash?
Or just found by sanitizer?
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
With best regards,
Slava
next prev parent reply other threads:[~2022-06-20 5:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 3:06 [dpdk-dev] [PATCH 1/1] net/mlx5: fix stack buffer overflow of hrxq's rss_key Yunjian Wang
2022-01-28 9:41 ` wangyunjian
2022-02-08 10:55 ` wangyunjian
2022-03-02 10:54 ` wangyunjian
2022-06-20 5:16 ` Slava Ovsiienko
2022-06-20 5:59 ` wangyunjian [this message]
2022-06-20 8:02 ` Raslan Darawsheh
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=3ce0eb9e4a8a46a4ad230715d9ec1878@huawei.com \
--to=wangyunjian@huawei.com \
--cc=dev@dpdk.org \
--cc=dingxiaoxiong@huawei.com \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.com \
--cc=xudingke@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.