From: Greg KH <gregkh@linuxfoundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: pabeni@redhat.com, davem@davemloft.net, kuba@kernel.org,
yoshfuji@linux-ipv6.org, kuznet@ms2.inr.ac.ru,
stable@vger.kernel.org
Subject: Re: [PATCH 0/2] backports for slab-out-of-bounds issue in ip6_xmit()
Date: Thu, 31 Dec 2020 10:17:55 +0100 [thread overview]
Message-ID: <X+2XQ1JRPSeKLtkK@kroah.com> (raw)
In-Reply-To: <20201230193323.2133009-1-surenb@google.com>
On Wed, Dec 30, 2020 at 11:33:21AM -0800, Suren Baghdasaryan wrote:
> We received a slab-out-of-bounds report in ip6_xmit() for KASAN build on 4.9
> kernel. The patches that fix this issue have been backported to to stable 4.14
> and one of them even to 3.16 but 4.9 stable branch does not include them.
> Backport to linux-4.9.y required trivial merge conflict resolution. They
> cleanly apply to linux-stable linux-4.9.y branch tagged v4.9.249.
>
> Paolo Abeni (2):
> net: ipv6: keep sk status consistent after datagram connect failure
> l2tp: fix races with ipv4-mapped ipv6 addresses
>
> net/ipv6/datagram.c | 21 +++++++++++++++++----
> net/l2tp/l2tp_core.c | 38 ++++++++++++++++++--------------------
> net/l2tp/l2tp_core.h | 3 ---
> 3 files changed, 35 insertions(+), 27 deletions(-)
Nit, you forgot to sign-off on these patches that you forwarded on.
Next time remember to do that as you did "touch" them :)
I'll go queue them up now.
thanks,
greg k-h
next prev parent reply other threads:[~2020-12-31 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 19:33 [PATCH 0/2] backports for slab-out-of-bounds issue in ip6_xmit() Suren Baghdasaryan
2020-12-30 19:33 ` [PATCH 1/2] net: ipv6: keep sk status consistent after datagram connect failure Suren Baghdasaryan
2020-12-30 19:33 ` [PATCH 2/2] l2tp: fix races with ipv4-mapped ipv6 addresses Suren Baghdasaryan
2020-12-31 9:17 ` Greg KH [this message]
2021-01-05 16:38 ` [PATCH 0/2] backports for slab-out-of-bounds issue in ip6_xmit() Suren Baghdasaryan
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=X+2XQ1JRPSeKLtkK@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=yoshfuji@linux-ipv6.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.