Re: Re: ACPI: sbshc: remove raw pointer from printk message

["wang_qize@venustech.com.cn" <wang_qize@venustech.com.cn>]

[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]


 I has recvied a cve-id from mitre.org for this security bug .
should this cve-id( CVE-2018-5750) be mentioned in kernel change log?



wang_qize@venustech.com.cn
 
From: Greg Kroah-Hartman
Date: 2018-01-20 16:16
To: Rafael J. Wysocki
CC: Rafael J. Wysocki; Len Brown; ACPI Devel Maling List; Linux Kernel Mailing List; Wang Qize
Subject: Re: ACPI: sbshc: remove raw pointer from printk message
On Sat, Jan 20, 2018 at 09:03:33AM +0100, Rafael J. Wysocki wrote:
> On Sat, Jan 20, 2018 at 8:36 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Sat, Jan 20, 2018 at 12:53:39AM +0100, Rafael J. Wysocki wrote:
> >> On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
> >> <gregkh@linuxfoundation.org> wrote:
> >> > There's no need to be printing a raw kernel pointer to the kernel log at
> >> > every boot.  So just remove it, and change the whole message to use the
> >> > correct dev_info() call at the same time.
> >> >
> >> > Reported-by: Wang Qize <wang_qize@venustech.com.cn>
> >> > Cc: stable <stable@vger.kernel.org>
> >>
> >> I will remember this one. ;-)
> >>
> >> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >>
> >> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >
> > Does that mean you want me to take this through my tree?  Or is there an
> > acpi tree it will go through?
> 
> I thought you'd push it, but I can take it, of course.  For 4.16, though.
 
4.16 is fine, the issue has been around for a very long time, no rush :)
 

[-- Attachment #2: Type: text/html, Size: 4263 bytes --]