From: Hangbin Liu <liuhangbin@gmail.com>
To: "David S . Miller" <davem@davemloft.net>
Cc: Jay Vosburgh <jay.vosburgh@canonical.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Jonathan Toppins <jtoppins@redhat.com>,
Paolo Abeni <pabeni@redhat.com>, David Ahern <dsahern@gmail.com>,
Liang Li <liali@redhat.com>, David Ahern <dsahern@kernel.org>
Subject: Re: [PATCHv3 net] bonding: fix ICMPv6 header handling when receiving IPv6 messages
Date: Wed, 16 Nov 2022 14:34:06 +0800 [thread overview]
Message-ID: <Y3SEXh0x4G7jNSi9@Laptop-X1> (raw)
In-Reply-To: <CANn89iKW60QdMRbpyaYry4Vdfxm41ifh4qFt1azU5FCYkUJBiA@mail.gmail.com>
On Wed, Nov 09, 2022 at 01:48:11PM -0800, Eric Dumazet wrote:
> On Wed, Nov 9, 2022 at 1:23 PM Jay Vosburgh <jay.vosburgh@canonical.com> wrote:
> >
> > Eric Dumazet <edumazet@google.com> wrote:
> > >Quite frankly I would simply use
> > >
> > >if (pskb_may_pull(skb, sizeof(struct ipv6hdr) + sizeof(struct icmp6hdr))
> > > instead of skb_header_pointer()
> > >because chances are high we will need the whole thing in skb->head later.
> >
> > Well, it was set up this way with skb_header_pointer() instead
> > of pskb_may_pull() by you in de063b7040dc ("bonding: remove packet
> > cloning in recv_probe()") so the bonding rx_handler wouldn't change or
> > clone the skb. Now, I'm not sure if we should follow your advice to go
> > against your advice.
>
> Ah... I forgot about this, thanks for reminding me it ;)
Hi David,
The patch state[1] is Changes Requested, but I think Eric has no object on this
patch now. Should I keep waiting, or re-send the patch?
[1] https://patchwork.kernel.org/project/netdevbpf/patch/20221109014018.312181-1-liuhangbin@gmail.com/
Thanks
Hangbin
next prev parent reply other threads:[~2022-11-16 6:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 1:40 [PATCHv3 net] bonding: fix ICMPv6 header handling when receiving IPv6 messages Hangbin Liu
2022-11-09 19:42 ` Jay Vosburgh
2022-11-09 20:17 ` Eric Dumazet
2022-11-09 20:39 ` Jay Vosburgh
2022-11-09 20:45 ` Eric Dumazet
2022-11-09 21:23 ` Jay Vosburgh
2022-11-09 21:48 ` Eric Dumazet
2022-11-16 6:34 ` Hangbin Liu [this message]
2022-11-16 15:16 ` Jay Vosburgh
2022-11-17 2:44 ` Hangbin Liu
2022-11-17 4:29 ` Jay Vosburgh
2022-11-17 8:34 ` Hangbin Liu
2022-11-17 10:27 ` Eric Dumazet
2022-11-17 20:04 ` Jay Vosburgh
2022-11-18 2:49 ` Hangbin Liu
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=Y3SEXh0x4G7jNSi9@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=jay.vosburgh@canonical.com \
--cc=jtoppins@redhat.com \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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