From: Kevin Traynor <ktraynor@redhat.com>
To: Xiao Zhang <xiao.zhang@intel.com>, dev@dpdk.org
Cc: beilei.xing@intel.com, qi.z.zhang@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] net/i40e: fix integer overflow
Date: Mon, 14 Oct 2019 11:35:48 +0100 [thread overview]
Message-ID: <d090d2c1-e8e4-fc24-83e5-f38abf020222@redhat.com> (raw)
In-Reply-To: <1571041986-37562-1-git-send-email-xiao.zhang@intel.com>
On 14/10/2019 09:33, Xiao Zhang wrote:
> When configuring i40e rx queue, the temporary variable to store max packet
> length is not big enough which leads to integer overflow issue. This
> patch is to fix the issue by changing the variable type from uint16_t
> to uint32_t.
>
> Fixes: c511a96a34d7 ("mbuf: add accessors for data room and private
> size")
It should be
Fixes: 4861cde46116 ("i40e: new poll mode driver")
> Cc: stable@dpdk.org
>
> Signed-off-by: Xiao Zhang <xiao.zhang@intel.com>
> ---
> drivers/net/i40e/i40e_rxtx.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/i40e/i40e_rxtx.c b/drivers/net/i40e/i40e_rxtx.c
> index bfe161f..ca15b12 100644
> --- a/drivers/net/i40e/i40e_rxtx.c
> +++ b/drivers/net/i40e/i40e_rxtx.c
> @@ -2596,7 +2596,8 @@ i40e_rx_queue_config(struct i40e_rx_queue *rxq)
> struct i40e_pf *pf = I40E_VSI_TO_PF(rxq->vsi);
> struct i40e_hw *hw = I40E_VSI_TO_HW(rxq->vsi);
> struct rte_eth_dev_data *data = pf->dev_data;
> - uint16_t buf_size, len;
> + uint16_t buf_size;
> + uint32_t len;
>
You can just remove the variable, it's only used once.
> buf_size = (uint16_t)(rte_pktmbuf_data_room_size(rxq->mp) -
> RTE_PKTMBUF_HEADROOM);
>
next prev parent reply other threads:[~2019-10-14 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 8:33 [dpdk-stable] " Xiao Zhang
2019-10-14 10:35 ` Kevin Traynor [this message]
2019-10-15 1:10 ` [dpdk-stable] [dpdk-dev] " Zhang, Xiao
2019-10-15 5:29 ` [dpdk-stable] [v2] " Xiao Zhang
2019-10-16 3:21 ` [dpdk-stable] [dpdk-dev] " Ye Xiaolong
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=d090d2c1-e8e4-fc24-83e5-f38abf020222@redhat.com \
--to=ktraynor@redhat.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=xiao.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).