From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from new4-smtp.messagingengine.com ([66.111.4.230]:33269 "EHLO new4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726477AbeKTTjo (ORCPT ); Tue, 20 Nov 2018 14:39:44 -0500 Date: Tue, 20 Nov 2018 10:11:36 +0100 From: Greg KH To: Jean Delvare Cc: stable@vger.kernel.org, Guenter Roeck , Erik Schmauss , "Rafael J. Wysocki" Subject: Re: Please revert "ACPICA: AML interpreter: add region addresses in global list during initialization" Message-ID: <20181120091136.GA20291@kroah.com> References: <20181120094649.243f9670@endymion> <20181120085419.GA19171@kroah.com> <20181120100359.3986a611@endymion> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181120100359.3986a611@endymion> Sender: stable-owner@vger.kernel.org List-ID: On Tue, Nov 20, 2018 at 10:03:59AM +0100, Jean Delvare wrote: > On Tue, 20 Nov 2018 09:54:19 +0100, Greg KH wrote: > > On Tue, Nov 20, 2018 at 09:46:49AM +0100, Jean Delvare wrote: > > > Dear stable kernel team, > > > > > > In stable kernel 4.19.2, the following upstream commit was included: > > > > > > commit 4abb951b73ff0a8a979113ef185651aa3c8da19b > > > Author: Erik Schmauss > > > Date: Wed Oct 17 14:09:35 2018 -0700 > > > > > > ACPICA: AML interpreter: add region addresses in global list during initialization > > > > > > (...) > > > Please revert this commit from future stable kernels on all affected > > > branches (I think only 4.18.19 and 4.19.2 are affected at the moment, > > > but maybe other affected releases are in the works already). > > > > Ok, I'll go revert this, but shouldn't it also be reverted in Linus's > > tree as well? > > No. As I understand it (with my limited knowledge of ACPICA), the > change itself is correct. The problem is that it will detect resource > conflicts which were unnoticed before, and that will prevent drivers > from loading. Some of them may be addressed with driver fixes or new > drivers. Others are false positives (due to bogus BIOS) which users > will have to work around with acpi_resource_conflicts=lax. We have been > through this before, nothing new really, but it takes years to address > such problems. This just can't be done in stable kernel series. Fair enough, I have seen reports about this already. Now reverted. thanks, greg k-h