From: David Miller <davem@davemloft.net>
To: asavkov@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jstancek@redhat.com, steffen.klassert@secunet.com,
alexander.h.duyck@intel.com
Subject: Re: [PATCH] ip6_offload: check segs for NULL in ipv6_gso_segment.
Date: Fri, 02 Dec 2016 13:36:36 -0500 (EST) [thread overview]
Message-ID: <20161202.133636.42467667676009914.davem@davemloft.net> (raw)
In-Reply-To: <1480597564-32355-1-git-send-email-asavkov@redhat.com>
From: Artem Savkov <asavkov@redhat.com>
Date: Thu, 1 Dec 2016 14:06:04 +0100
> segs needs to be checked for being NULL in ipv6_gso_segment() before calling
> skb_shinfo(segs), otherwise kernel can run into a NULL-pointer dereference:
...
> Signed-off-by: Artem Savkov <asavkov@redhat.com>
Applied and queued up for -stable.
prev parent reply other threads:[~2016-12-02 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 13:06 [PATCH] ip6_offload: check segs for NULL in ipv6_gso_segment Artem Savkov
2016-12-01 14:34 ` Eric Dumazet
2016-12-01 15:07 ` Artem Savkov
2016-12-01 15:27 ` Eric Dumazet
2016-12-01 15:19 ` Eric Dumazet
2016-12-02 18:36 ` David Miller [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=20161202.133636.42467667676009914.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.h.duyck@intel.com \
--cc=asavkov@redhat.com \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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