From: David Miller <davem@davemloft.net>
To: ben@decadent.org.uk
Cc: machida.yuki@jp.fujitsu.com, netdev@vger.kernel.org
Subject: Re: [requrest for stable 4.1.y inclution] Fix for CVE-2015-7799
Date: Fri, 15 Jan 2016 16:01:01 -0500 (EST) [thread overview]
Message-ID: <20160115.160101.1790770055744457023.davem@davemloft.net> (raw)
In-Reply-To: <1452777529.7020.67.camel@decadent.org.uk>
From: Ben Hutchings <ben@decadent.org.uk>
Date: Thu, 14 Jan 2016 13:18:49 +0000
> On Thu, 2016-01-14 at 20:56 +0900, Yuki Machida wrote:
>> This patch is the fix for CVE-2015-7799
>> Upstream commit 4ab42d78e37a294ac7bc56901d563c642e03c4ae
>>
>> Stable 3.2.y has included this patch in v3.2.75.
>> https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.2.75
>>
>> Please include in this patch to stable 4.1.y.
>
> Commit 0baa57d8dc32db78369d8b5176ef56c5e2e18ab3 is also needed as
> preparation.
Noted, thanks Ben.
next prev parent reply other threads:[~2016-01-15 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 11:56 [requrest for stable 4.1.y inclution] Fix for CVE-2015-7799 Yuki Machida
2016-01-14 13:18 ` Ben Hutchings
2016-01-15 2:52 ` Yuki Machida
2016-01-15 21:01 ` David Miller [this message]
2016-01-15 21:00 ` David Miller
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=20160115.160101.1790770055744457023.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ben@decadent.org.uk \
--cc=machida.yuki@jp.fujitsu.com \
--cc=netdev@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