From: Yuki Machida <machida.yuki@jp.fujitsu.com>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org
Subject: Re: CVE-2015-7885 security fix for stable
Date: Fri, 19 Feb 2016 17:02:46 +0900 [thread overview]
Message-ID: <56C6CC26.4060102@jp.fujitsu.com> (raw)
In-Reply-To: <20160127065154.GB5356@kroah.com>
Thank you for your reply.
Sorry for the delay.
On 2016年01月27日 15:51, Greg KH wrote:
> 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?
Possibility of using this hardware is very low.
Based on the story described above, it does not use this hardware.
Please stop this fix.
Thank you for your advice.
Yuki Machida.
>
> thanks,
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-02-19 8:02 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
2016-02-19 8:02 ` Yuki Machida [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=56C6CC26.4060102@jp.fujitsu.com \
--to=machida.yuki@jp.fujitsu.com \
--cc=greg@kroah.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).