From: Sasha Levin <sashal@kernel.org>
To: Peter Oskolkov <posk@posk.io>
Cc: Captain Wiggum <captwiggum@gmail.com>,
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 19:15:11 -0400 [thread overview]
Message-ID: <20190408231511.GJ4689@sasha-vm> (raw)
In-Reply-To: <CAFTs51UirJyCdjqngm=4vXXUP8-uBiGYqo9OU_rkn8B=iqzn-w@mail.gmail.com>
On Mon, Apr 08, 2019 at 10:13:57AM -0700, Peter Oskolkov wrote:
>On Mon, Apr 8, 2019 at 9:29 AM Captain Wiggum <captwiggum@gmail.com> wrote:
>>
>> Thank you Peter!
>>
>> I tried the patch on 4.9.167 & 4.19.32. It's out of sync with upstream.
>> Looks like a little different work needed for each LTS kernel.
>> Is someone is familiar with it, and is available to patch it?
>
>I'll try to backport the patchset to 4.9 and send it out for review.
>If it is accepted (this
>will be my first stable backport attempt), I'll do the same for 4.14 and 4.19.
Please start with 4.19 and work backwards for two reasons:
1. If we fix something in 4.9, and the user upgrades to a broken
4.14/4.19 he'll be very upset.
2. It'll make the backporting process much easier for you as the
differences between 4.19 and 5.0 are much smaller than 4.9 and 5.0.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-04-08 23:15 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
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 [this message]
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=20190408231511.GJ4689@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=posk@posk.io \
--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.