From: David Miller <davem@davemloft.net>
To: willemdebruijn.kernel@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH RFC 11/12] net: Remove all references to SKB_GSO_UDP.
Date: Thu, 06 Jul 2017 15:20:23 +0100 (WEST) [thread overview]
Message-ID: <20170706.152023.1317350139656231489.davem@davemloft.net> (raw)
In-Reply-To: <CAF=yD-+nZMDnAgHkT=hDONA1mtB3r4F2nct0aVuUtA8tXp9RLw@mail.gmail.com>
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Date: Wed, 5 Jul 2017 13:21:02 -0400
> On Wed, Jul 5, 2017 at 12:06 PM, Willem de Bruijn
> <willemdebruijn.kernel@gmail.com> wrote:
>>> diff --git a/include/linux/virtio_net.h b/include/linux/virtio_net.h
>>> index 5209b5e..32fb046 100644
>>> --- a/include/linux/virtio_net.h
>>> +++ b/include/linux/virtio_net.h
>>> @@ -18,9 +18,6 @@ static inline int virtio_net_hdr_to_skb(struct sk_buff *skb,
>>> case VIRTIO_NET_HDR_GSO_TCPV6:
>>> gso_type = SKB_GSO_TCPV6;
>>> break;
>>> - case VIRTIO_NET_HDR_GSO_UDP:
>>> - gso_type = SKB_GSO_UDP;
>>> - break;
>>
>> Virtio devices negotiate feature support before using this, but
>> tuntap and pf_packet may be passing these packets unconditionally.
>> Perhaps we should fragment those on the spot with skb_segment.
>
> Tun has ioctl TUNSETIFF to probe for features and it can be argued
> that packet sockets should query device features with ethtool before
> relying on them. So perhaps we don't need to fix this up, after all.
Yes, this is the same thought process I went through, and the same
conclusion I arrived at. :-)
prev parent reply other threads:[~2017-07-06 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 15:06 [PATCH RFC 11/12] net: Remove all references to SKB_GSO_UDP David Miller
2017-07-05 16:06 ` Willem de Bruijn
2017-07-05 16:27 ` Willem de Bruijn
2017-07-06 14:43 ` David Miller
2017-07-06 17:57 ` Willem de Bruijn
2017-07-07 9:46 ` David Miller
2017-07-05 17:21 ` Willem de Bruijn
2017-07-06 14:20 ` David Miller [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=20170706.152023.1317350139656231489.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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 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).