Date: Wed, 13 Dec 2017 06:52:01 -0800
From: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
        "lenb@kernel.org" <lenb@kernel.org>,
        "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
        "devel@acpica.org" <devel@acpica.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "vadim.lomovtsev@cavium.com" <vadim.lomovtsev@cavium.com>,
        "Schmauss, Erik" <erik.schmauss@intel.com>
Subject: Re: [PATCH] acpi: acpica: add acpi status check prior walking
 through namespace
Message-ID: <20171213145201.GA6692@localhost.localdomain>
References: <1513094360-1414-1-git-send-email-Vadim.Lomovtsev@caviumnetworks.com>
 <1513094360-1414-2-git-send-email-Vadim.Lomovtsev@caviumnetworks.com>
 <94F2FBAB4432B54E8AACC7DFDE6C92E3B74FBD84@ORSMSX110.amr.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E3B74FBD84@ORSMSX110.amr.corp.intel.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Dec 2017 14:52:05.7178 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 794b2c1d-54ad-46fa-3848-08d54239147e
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 711e4ccf-2e9b-4bcf-a551-4094005b6194
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR07MB3002
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2421
Lines: 66

On Tue, Dec 12, 2017 at 09:52:21PM +0000, Moore, Robert wrote:
> Another way to look at this is that the kernel should not be calling ACPI interfaces if ACPI is disabled.

Yes, I agree. So in this case the ltp_acpi test case has to be updated with such checking
before calling ACPI interfaces. However, it seems that such calls was put there intentionally,
without ACPI state check, as part of kernel testing strategy.

WBR,
Vadim

> 
> > -----Original Message-----
> > From: Vadim Lomovtsev [mailto:Vadim.Lomovtsev@caviumnetworks.com]
> > Sent: Tuesday, December 12, 2017 7:59 AM
> > To: Moore, Robert <robert.moore@intel.com>; Zheng, Lv
> > <lv.zheng@intel.com>; Wysocki, Rafael J <rafael.j.wysocki@intel.com>;
> > lenb@kernel.org; linux-acpi@vger.kernel.org; devel@acpica.org; linux-
> > kernel@vger.kernel.org
> > Cc: vadim.lomovtsev@cavium.com
> > Subject: [PATCH] acpi: acpica: add acpi status check prior walking
> > through namespace
> > 
> > From: Vadim Lomovtsev <vadim.lomovtsev@cavium.com>
> > 
> > While having kernel built with ACPI support enabled and booted over FDT,
> > the ltp_acpi test from LTP suite causes kernel crash while calling
> > acpi_ns_walk_namespace(). The acpi_get_devices is high level wrapper for
> > it, so we need to protect kernel from crashes by adding acpi status
> > check before walking through namespace which is not loaded because of
> > acpi is disabled.
> > 
> > Signed-off-by: Vadim Lomovtsev <vadim.lomovtsev@cavium.com>
> > ---
> >  drivers/acpi/acpica/nsxfeval.c | 7 +++++++
> >  1 file changed, 7 insertions(+)
> > 
> > diff --git a/drivers/acpi/acpica/nsxfeval.c
> > b/drivers/acpi/acpica/nsxfeval.c index 783f4c8..e0eb9ae 100644
> > --- a/drivers/acpi/acpica/nsxfeval.c
> > +++ b/drivers/acpi/acpica/nsxfeval.c
> > @@ -52,6 +52,8 @@
> >  #define _COMPONENT          ACPI_NAMESPACE
> >  ACPI_MODULE_NAME("nsxfeval")
> > 
> > +extern int acpi_disabled;
> > +
> >  /* Local prototypes */
> >  static void acpi_ns_resolve_references(struct acpi_evaluate_info
> > *info);
> > 
> > @@ -812,6 +814,11 @@ static void acpi_ns_resolve_references(struct
> > acpi_evaluate_info *info)
> > 
> >  	ACPI_FUNCTION_TRACE(acpi_get_devices);
> > 
> > +	/* check if ACPI disabled to prevent kernel crash later */
> > +	if (acpi_disabled) {
> > +		return_ACPI_STATUS(AE_NOT_CONFIGURED);
> > +	}
> > +
> >  	/* Parameter validation */
> > 
> >  	if (!user_function) {
> > --
> > 1.8.3.1
>