From: Sasha Levin <sashal@kernel.org>
To: Captain Wiggum <captwiggum@gmail.com>
Cc: davem@davemloft.net,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Florian Westphal <fw@strlen.de>,
Eric Dumazet <edumazet@google.com>,
Peter Oskolkov <posk@google.com>,
netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] ipv6: un-do: defrag: drop non-last frags smaller than min mtu
Date: Mon, 8 Apr 2019 11:51:27 -0400 [thread overview]
Message-ID: <20190408155127.GH4689@sasha-vm> (raw)
In-Reply-To: <CAB=W+okxdCdQG8opakm1BHf+W7wfGuoocU1YoDfokMDyPk2_Tw@mail.gmail.com>
On Mon, Apr 08, 2019 at 08:49:52AM -0600, Captain Wiggum wrote:
>Hi Sasha,
>
>This patch cannot be applied to upstream, the code is significantly different.
>Therefore, this un-do patch would not be seen in the upstream git log.
>It was solved there by coding a better solution, not by the un-do patch.
Okay, so this is effectively a request to diverge the -stable tree from
upstream in a non-trivial way, which is why I asked David Miller to ack
this act explcitly (or to send me patches, or whatever else he thinks is
appropriate here).
>Please consider this:
>Upstream passes the TAHI IPv6 protocol tests. All the LTS kernels do NOT.
>This is the patch that causes the failure in 4.9, 4.14, 4.19 LTS kernels.
I very much agree that this should get fixed. My concerns are not with
the bug but are with the proposed fix as it applies to -stable trees.
>And this patch has been in place with 4.9.134, a long time.
>It is not right that "Linux" can not pass the IPv6 protocol test.
>My executive are asking me why "Linux" is not fit for IPv6 deployments.
Arguments such as this carry no weight in a more technical discussion
such as this. Yes, some tests are currently broken, but we will not take
shortcuts just because "executives are unhappy".
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-04-08 15:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 0:18 [PATCH net] ipv6: un-do: defrag: drop non-last frags smaller than min mtu Captain Wiggum
2019-04-05 4:50 ` Greg Kroah-Hartman
2019-04-05 16:22 ` Captain Wiggum
2019-04-06 14:15 ` Sasha Levin
2019-04-06 16:34 ` Florian Westphal
2019-04-08 14:49 ` Captain Wiggum
2019-04-08 14:54 ` Eric Dumazet
2019-04-08 15:09 ` Captain Wiggum
2019-04-08 15:51 ` Sasha Levin [this message]
2019-04-08 15:59 ` Peter Oskolkov
2019-04-08 16:29 ` Captain Wiggum
2019-04-08 17:13 ` Peter Oskolkov
2019-04-08 23:15 ` Sasha Levin
2019-04-08 23:38 ` Peter Oskolkov
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=20190408155127.GH4689@sasha-vm \
--to=sashal@kernel.org \
--cc=captwiggum@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=posk@google.com \
--cc=stable@vger.kernel.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 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.