From: Greg KH <gregkh@linuxfoundation.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: stable@vger.kernel.org, Ales Novak <alnovak@suse.cz>,
Seunghun Han <kkamagui@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Vikas C Sajjan <vikas.cha.sajjan@hpe.com>,
Sunil V L <sunil.vl@hpe.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: Regression caused by commit dad5ab0db8de ("x86/acpi: Prevent out of bound access caused by broken ACPI tables")
Date: Thu, 11 Jan 2018 08:19:05 +0100 [thread overview]
Message-ID: <20180111071905.GA2950@kroah.com> (raw)
In-Reply-To: <20180110210318.73430ed0@endymion>
On Wed, Jan 10, 2018 at 09:03:18PM +0100, Jean Delvare wrote:
> Hi Greg,
>
> On Wed, 10 Jan 2018 20:10:44 +0100, Greg KH wrote:
> > Many thanks for the report, I've queued up 252714155f04 now. I don't
> > think 4ee2ec1b1225 needs to be merged, unless the acpi maintainers think
> > it is a good idea to do so.
> >
> > Rafael, any thoughts?
>
> FWIW we applied both in SUSE kernels. I did not make the decision but I
> approve it. Having duplicated code in our kernel when there's only one
> occurrence of the same code upstream looks dangerous. If there ever is
> a bug fixed in that function and we backport the fix, you can be sure
> that only one of the copies will get fixed and the bug will remain in
> the other.
Good idea, I've now queued it up as well, thanks.
greg k-h
prev parent reply other threads:[~2018-01-11 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 18:28 Regression caused by commit dad5ab0db8de ("x86/acpi: Prevent out of bound access caused by broken ACPI tables") Jean Delvare
2018-01-10 19:10 ` Greg KH
2018-01-10 20:03 ` Jean Delvare
2018-01-11 7:19 ` Greg KH [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=20180111071905.GA2950@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alnovak@suse.cz \
--cc=jdelvare@suse.de \
--cc=kkamagui@gmail.com \
--cc=mingo@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.org \
--cc=sunil.vl@hpe.com \
--cc=tglx@linutronix.de \
--cc=vikas.cha.sajjan@hpe.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;
as well as URLs for NNTP newsgroup(s).