From: Peter Oskolkov <posk@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, netdev@vger.kernel.org
Cc: Peter Oskolkov <posk@posk.io>, David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Sasha Levin <sashal@kernel.org>,
Captain Wiggum <captwiggum@gmail.com>,
Peter Oskolkov <posk@google.com>
Subject: [PATCH 4.19 stable 0/3] net: ip6 defrag: backport fixes
Date: Mon, 8 Apr 2019 17:10:02 -0700 [thread overview]
Message-ID: <20190409001005.255869-1-posk@google.com> (raw)
Currently, 4.19 and earlier stable kernels contain a security fix
that is not fully IPv6 standard compliant.
This patchset backports IPv6 defrag fixes from 5.1rc that restore
standard-compliance.
Original 5.1 patchet: https://patchwork.ozlabs.org/cover/1029418/
John Masinter (captwiggum), could you, please, confirm that this
patchset fixes TAHI tests?
Peter Oskolkov (3):
net: IP defrag: encapsulate rbtree defrag code into callable functions
net: IP6 defrag: use rbtrees for IPv6 defrag
net: IP6 defrag: use rbtrees in nf_conntrack_reasm.c
include/net/inet_frag.h | 16 +-
include/net/ipv6_frag.h | 11 +-
net/ipv4/inet_fragment.c | 293 ++++++++++++++++++++++++
net/ipv4/ip_fragment.c | 290 +++--------------------
net/ipv6/netfilter/nf_conntrack_reasm.c | 260 ++++++---------------
net/ipv6/reassembly.c | 233 +++++--------------
6 files changed, 477 insertions(+), 626 deletions(-)
--
2.21.0.392.gf8f6787159e-goog
next reply other threads:[~2019-04-09 0:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 0:10 Peter Oskolkov [this message]
2019-04-09 0:10 ` [PATCH 4.19 stable 1/3] net: IP defrag: encapsulate rbtree defrag code into callable functions Peter Oskolkov
2019-04-09 0:10 ` [PATCH 4.19 stable 2/3] net: IP6 defrag: use rbtrees for IPv6 defrag Peter Oskolkov
2019-04-09 0:10 ` [PATCH 4.19 stable 3/3] net: IP6 defrag: use rbtrees in nf_conntrack_reasm.c Peter Oskolkov
2019-04-14 18:28 ` [PATCH 4.19 stable 0/3] net: ip6 defrag: backport fixes Captain Wiggum
2019-04-17 17:51 ` Captain Wiggum
2019-04-17 20:53 ` Sasha Levin
2019-04-19 18:55 ` David Miller
2019-04-22 0:42 ` Sasha Levin
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=20190409001005.255869-1-posk@google.com \
--to=posk@google.com \
--cc=captwiggum@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=posk@posk.io \
--cc=sashal@kernel.org \
--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).