netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heng Qi <hengqi@linux.alibaba.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, mst@redhat.com,
	jasowang@redhat.com, pabeni@redhat.com, kuba@kernel.org,
	john.fastabend@gmail.com, davem@davemloft.net,
	daniel@iogearbox.net, ast@kernel.org, edumazet@google.com,
	xuanzhuo@linux.alibaba.com
Subject: Re: [PATCH net-next v2] virtio-net: fix possible unsigned integer overflow
Date: Thu, 02 Feb 2023 06:20:16 +0000	[thread overview]
Message-ID: <167531881698.1809.4464102208743775598.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230131085004.98687-1-hengqi@linux.alibaba.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 31 Jan 2023 16:50:04 +0800 you wrote:
> When the single-buffer xdp is loaded and after xdp_linearize_page()
> is called, *num_buf becomes 0 and (*num_buf - 1) may overflow into
> a large integer in virtnet_build_xdp_buff_mrg(), resulting in
> unexpected packet dropping.
> 
> Fixes: ef75cb51f139 ("virtio-net: build xdp_buff with multi buffers")
> Signed-off-by: Heng Qi <hengqi@linux.alibaba.com>
> Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> 
> [...]

Here is the summary with links:
  - [net-next,v2] virtio-net: fix possible unsigned integer overflow
    https://git.kernel.org/netdev/net-next/c/981f14d42a7f

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



  reply	other threads:[~2023-02-02  6:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31  8:50 [PATCH net-next v2] virtio-net: fix possible unsigned integer overflow Heng Qi
2023-02-02  6:20 ` patchwork-bot+netdevbpf [this message]
2023-02-02  8:07 ` Michael S. Tsirkin
2023-02-02  8:14   ` Heng Qi
2023-02-02  8:16     ` Michael S. Tsirkin
2023-02-02  9:07       ` Heng Qi
2023-02-02 10:31         ` Michael S. Tsirkin
2023-02-02 10:55           ` Heng Qi

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=167531881698.1809.4464102208743775598.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hengqi@linux.alibaba.com \
    --cc=jasowang@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xuanzhuo@linux.alibaba.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).