All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com,
	davem@davemloft.net, kuba@kernel.org, jtoppins@redhat.com,
	pabeni@redhat.com, dsahern@gmail.com, tom@herbertland.com,
	edumazet@google.com, liali@redhat.com, eric.dumazet@gmail.com
Subject: Re: [PATCHv4 net] bonding: fix ICMPv6 header handling when receiving IPv6 messages
Date: Sat, 19 Nov 2022 03:50:18 +0000	[thread overview]
Message-ID: <166882981815.27279.7611867364193696030.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221118034353.1736727-1-liuhangbin@gmail.com>

Hello:

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

On Fri, 18 Nov 2022 11:43:53 +0800 you wrote:
> Currently, we get icmp6hdr via function icmp6_hdr(), which needs the skb
> transport header to be set first. But there is no rule to ask driver set
> transport header before netif_receive_skb() and bond_handle_frame(). So
> we will not able to get correct icmp6hdr on some drivers.
> 
> Fix this by using skb_header_pointer to get the IPv6 and ICMPV6 headers.
> 
> [...]

Here is the summary with links:
  - [PATCHv4,net] bonding: fix ICMPv6 header handling when receiving IPv6 messages
    https://git.kernel.org/netdev/net/c/4d633d1b468b

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



      parent reply	other threads:[~2022-11-19  3:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  3:43 [PATCHv4 net] bonding: fix ICMPv6 header handling when receiving IPv6 messages Hangbin Liu
2022-11-18  3:56 ` Eric Dumazet
2022-11-18  4:36 ` Jay Vosburgh
2022-11-19  3:50 ` 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=166882981815.27279.7611867364193696030.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=j.vosburgh@gmail.com \
    --cc=jtoppins@redhat.com \
    --cc=kuba@kernel.org \
    --cc=liali@redhat.com \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tom@herbertland.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.