From: Sasha Levin <sashal@kernel.org>
To: Peter Oskolkov <posk@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, netdev@vger.kernel.org,
Peter Oskolkov <posk@posk.io>, David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Captain Wiggum <captwiggum@gmail.com>,
Lars Persson <lists@bofh.nu>
Subject: Re: [PATCH 4.19 stable v2 0/3] net: ip6 defrag: backport fixes
Date: Tue, 23 Apr 2019 19:47:28 -0400 [thread overview]
Message-ID: <20190423234728.GV17719@sasha-vm> (raw)
In-Reply-To: <20190423172533.245939-1-posk@google.com>
On Tue, Apr 23, 2019 at 10:25:30AM -0700, Peter Oskolkov wrote:
>Lars Persson <lists@bofh.nu> reported that a label was unused in
>the 4.14 version of this patchset, and the issue was present in
>the 4.19 patchset as well, so I'm sending a v2 that fixes it.
>
>The original 4.19 patchset queued for stable is OK, and
>can be used as is, but this v2 is a bit better: it fixes the
>unused label issue and handles overlapping fragments better.
>
>Sorry for the mess/v2.
I've replace the patches in 4.19, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-04-23 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 17:25 [PATCH 4.19 stable v2 0/3] net: ip6 defrag: backport fixes Peter Oskolkov
2019-04-23 17:25 ` [PATCH 4.19 stable v2 1/3] net: IP defrag: encapsulate rbtree defrag code into callable functions Peter Oskolkov
2019-04-23 17:25 ` [PATCH 4.19 stable v2 2/3] net: IP6 defrag: use rbtrees for IPv6 defrag Peter Oskolkov
2019-04-23 17:25 ` [PATCH 4.19 stable v2 3/3] net: IP6 defrag: use rbtrees in nf_conntrack_reasm.c Peter Oskolkov
2019-04-23 23:47 ` Sasha Levin [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=20190423234728.GV17719@sasha-vm \
--to=sashal@kernel.org \
--cc=captwiggum@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=lists@bofh.nu \
--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 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).