From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: xiyou.wangcong@gmail.com, linux@stwm.de, netdev@vger.kernel.org,
eric.dumazet@gmail.com, therbert@google.com
Subject: Re: [PATCH net v3] ipv4: ipv6: better estimate tunnel header cut for correct ufo handling
Date: Wed, 26 Feb 2014 13:45:58 -0500 (EST) [thread overview]
Message-ID: <20140226.134558.1764489422685253686.davem@davemloft.net> (raw)
In-Reply-To: <20140226134735.GD24855@order.stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Wed, 26 Feb 2014 14:47:35 +0100
> This bug is present and was reported on v3.13 kernels, so I also would propose
> this for v3.13. I hoped it would be clear from the thread, but should have
> stated this more clearly.
>
> It really is only appropriate there as this problem was introduced with
> 61c1db7fae21ed ("ipv6: sit: add GSO/TSO support") and cb32f511a70be8
> ("ipip: add GSO/TSO support"), both introduced in v3.13.
Ok, queued up for -stable, thanks.
next prev parent reply other threads:[~2014-02-26 18:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 17:47 linux 3.13: problems with isatap tunnel device and UFO Wolfgang Walter
2014-02-07 17:56 ` Hannes Frederic Sowa
2014-02-07 18:17 ` Wolfgang Walter
2014-02-07 22:22 ` Hannes Frederic Sowa
2014-02-08 23:17 ` Wolfgang Walter
2014-02-11 2:44 ` Hannes Frederic Sowa
2014-02-11 17:42 ` Wolfgang Walter
2014-02-17 16:09 ` Hannes Frederic Sowa
2014-02-20 2:44 ` Hannes Frederic Sowa
2014-02-20 2:54 ` Hannes Frederic Sowa
2014-02-21 0:43 ` Cong Wang
2014-02-21 1:19 ` Hannes Frederic Sowa
2014-02-23 21:05 ` [PATCH net] ipv4: ipv6: better estimate tunnel header cut for correct ufo handling Hannes Frederic Sowa
2014-02-23 21:24 ` [PATCH net v2] " Hannes Frederic Sowa
2014-02-23 23:48 ` [PATCH net v3] " Hannes Frederic Sowa
2014-02-25 23:27 ` David Miller
2014-02-26 13:47 ` Hannes Frederic Sowa
2014-02-26 18:45 ` David Miller [this message]
2014-03-07 14:13 ` Wolfgang Walter
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=20140226.134558.1764489422685253686.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=linux@stwm.de \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
--cc=xiyou.wangcong@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).