From: Greg KH <greg@kroah.com>
To: Yuki Machida <machida.yuki@jp.fujitsu.com>
Cc: stable@vger.kernel.org
Subject: Re: CVE-2015-7885 security fix for stable
Date: Tue, 26 Jan 2016 22:51:54 -0800 [thread overview]
Message-ID: <20160127065154.GB5356@kroah.com> (raw)
In-Reply-To: <56989C9F.6020305@jp.fujitsu.com>
On Fri, Jan 15, 2016 at 04:15:43PM +0900, Yuki Machida wrote:
> > Could you please apply this CVE-2015-7884 fix for -stable?
> Correct CVE Number is CVE-2015-7885.
> sorry.
>
> On 2016年01月15日 15:22, Yuki Machida wrote:
> > Hi, Greg
> >
> > Could you please apply this CVE-2015-7884 fix for -stable?
> > commit 4b6184336ebb5c8dc1eae7f7ab46ee608a748b05
Why, do you have access to this hardware? Do you know anyone that does?
The driver has much worse problems than this and is about to be deleted
from the tree given that it does not even work, so I don't see how
adding a backport for this code will help anyone out.
Do you?
thanks,
greg k-h
next prev parent reply other threads:[~2016-01-27 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 6:22 CVE-2015-7885 security fix for stable Yuki Machida
2016-01-15 7:15 ` Yuki Machida
2016-01-27 6:51 ` Greg KH [this message]
2016-02-19 8:02 ` Yuki Machida
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=20160127065154.GB5356@kroah.com \
--to=greg@kroah.com \
--cc=machida.yuki@jp.fujitsu.com \
--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).