All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Wong Vee Khee <vee.khee.wong@linux.intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
	joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
	mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v1 1/1] net: stmmac: Fix potential integer overflow
Date: Fri, 11 Jun 2021 20:20:08 +0000	[thread overview]
Message-ID: <162344280841.13501.12129405164687324305.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210611090238.1157557-1-vee.khee.wong@linux.intel.com>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Fri, 11 Jun 2021 17:02:38 +0800 you wrote:
> The commit d96febedfde2 ("net: stmmac: arrange Tx tail pointer update
> to stmmac_flush_tx_descriptors") introduced the following coverity
> warning:-
> 
>   1. Unintentional integer overflow (OVERFLOW_BEFORE_WIDEN)
>      overflow_before_widen: Potentially overflowing expression
>      'tx_q->cur_tx * desc_size' with type 'unsigned int' (32 bits,
>      unsigned) is evaluated using 32-bit arithmetic, and then used in a
>      context that expects an expression of type dma_addr_t (64 bits,
>      unsigned).
> 
> [...]

Here is the summary with links:
  - [net-next,v1,1/1] net: stmmac: Fix potential integer overflow
    https://git.kernel.org/netdev/net-next/c/52e597d3e2e6

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Wong Vee Khee <vee.khee.wong@linux.intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
	joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
	mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v1 1/1] net: stmmac: Fix potential integer overflow
Date: Fri, 11 Jun 2021 20:20:08 +0000	[thread overview]
Message-ID: <162344280841.13501.12129405164687324305.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210611090238.1157557-1-vee.khee.wong@linux.intel.com>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Fri, 11 Jun 2021 17:02:38 +0800 you wrote:
> The commit d96febedfde2 ("net: stmmac: arrange Tx tail pointer update
> to stmmac_flush_tx_descriptors") introduced the following coverity
> warning:-
> 
>   1. Unintentional integer overflow (OVERFLOW_BEFORE_WIDEN)
>      overflow_before_widen: Potentially overflowing expression
>      'tx_q->cur_tx * desc_size' with type 'unsigned int' (32 bits,
>      unsigned) is evaluated using 32-bit arithmetic, and then used in a
>      context that expects an expression of type dma_addr_t (64 bits,
>      unsigned).
> 
> [...]

Here is the summary with links:
  - [net-next,v1,1/1] net: stmmac: Fix potential integer overflow
    https://git.kernel.org/netdev/net-next/c/52e597d3e2e6

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2021-06-11 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  9:02 [PATCH net-next v1 1/1] net: stmmac: Fix potential integer overflow Wong Vee Khee
2021-06-11  9:02 ` Wong Vee Khee
2021-06-11 20:20 ` patchwork-bot+netdevbpf [this message]
2021-06-11 20:20   ` patchwork-bot+netdevbpf

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=162344280841.13501.12129405164687324305.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=davem@davemloft.net \
    --cc=joabreu@synopsys.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=vee.khee.wong@linux.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 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.