From: David Miller <davem@davemloft.net>
To: dja@axtens.net
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org,
jasowang@redhat.com, pshelar@ovn.org, marcelo.leitner@gmail.com,
Manish.Chopra@cavium.com, dev@openvswitch.org
Subject: Re: [PATCH v2 0/4] Check size of packets before sending
Date: Mon, 29 Jan 2018 11:37:08 -0500 (EST) [thread overview]
Message-ID: <20180129.113708.981601083065136615.davem@davemloft.net> (raw)
In-Reply-To: <87h8r5s63p.fsf@linkitivity.dja.id.au>
From: Daniel Axtens <dja@axtens.net>
Date: Mon, 29 Jan 2018 14:20:58 +1100
> OK, so how about:
>
> - first, a series that introduces skb_gso_validate_mac_len and uses it
> in bnx2x. This should be backportable without difficulty.
>
> - then, a series that wires skb_gso_validate_mac_len into the core -
> validate_xmit_skb for instance, and reverts the bnx2x fix. This would
> not need to be backported.
>
> If that's an approach we can agree on, I am ready to send it when
> net-next opens again.
Please send the bnx2x specific fix now, thank you.
next prev parent reply other threads:[~2018-01-29 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 4:31 [PATCH v2 0/4] Check size of packets before sending Daniel Axtens
2018-01-25 4:31 ` [PATCH v2 1/4] net: rename skb_gso_validate_mtu -> skb_gso_validate_network_len Daniel Axtens
2018-01-25 4:31 ` [PATCH v2 2/4] net: move skb_gso_mac_seglen to skbuff.h Daniel Axtens
2018-01-25 4:31 ` [PATCH v2 3/4] net: is_skb_forwardable: check the size of GSO segments Daniel Axtens
2018-01-25 4:31 ` [PATCH v2 4/4] net: check the size of a packet in validate_xmit_skb Daniel Axtens
2018-01-25 12:40 ` [PATCH v2 0/4] Check size of packets before sending Eric Dumazet
[not found] ` <1516884036.3715.45.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-25 13:44 ` Daniel Axtens
2018-01-25 14:35 ` Eric Dumazet
2018-01-29 3:20 ` Daniel Axtens
2018-01-29 16:37 ` David Miller [this message]
[not found] ` <20180125043109.28332-1-dja-Yfaxwxk/+vWsTnJN9+BGXg@public.gmane.org>
2018-01-25 15:24 ` Marcelo Ricardo Leitner
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=20180129.113708.981601083065136615.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Manish.Chopra@cavium.com \
--cc=dev@openvswitch.org \
--cc=dja@axtens.net \
--cc=eric.dumazet@gmail.com \
--cc=jasowang@redhat.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
/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).