All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	oliver.graute@gmail.com, sagi@grimberg.me,
	viro@zeniv.linux.org.uk, hch@lst.de, alexander.duyck@gmail.com,
	eric.dumazet@gmail.com, willemb@google.com
Subject: Re: [PATCH net v2] udp: fix skb_copy_and_csum_datagram with odd segment sizes
Date: Fri, 05 Feb 2021 04:20:07 +0000	[thread overview]
Message-ID: <161249880719.20393.11679190126322875011.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210203192952.1849843-1-willemdebruijn.kernel@gmail.com>

Hello:

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

On Wed,  3 Feb 2021 14:29:52 -0500 you wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> When iteratively computing a checksum with csum_block_add, track the
> offset "pos" to correctly rotate in csum_block_add when offset is odd.
> 
> The open coded implementation of skb_copy_and_csum_datagram did this.
> With the switch to __skb_datagram_iter calling csum_and_copy_to_iter,
> pos was reinitialized to 0 on each call.
> 
> [...]

Here is the summary with links:
  - [net,v2] udp: fix skb_copy_and_csum_datagram with odd segment sizes
    https://git.kernel.org/netdev/net/c/52cbd23a119c

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



      parent reply	other threads:[~2021-02-05  4:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 19:29 [PATCH net v2] udp: fix skb_copy_and_csum_datagram with odd segment sizes Willem de Bruijn
2021-02-03 20:54 ` Alexander Duyck
2021-02-04 15:04 ` Eric Dumazet
2021-02-05  4:20 ` patchwork-bot+netdevbpf [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=161249880719.20393.11679190126322875011.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexander.duyck@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=hch@lst.de \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oliver.graute@gmail.com \
    --cc=sagi@grimberg.me \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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.