From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Shevchenko Subject: Re: [PATCH v2 2/6] ACPI / bus: Do not traverse through non-existed device table Date: Thu, 01 Feb 2018 22:40:46 +0200 Message-ID: <1517517646.7000.1446.camel@linux.intel.com> References: <20180201202012.36524-1-andriy.shevchenko@linux.intel.com> <20180201202012.36524-2-andriy.shevchenko@linux.intel.com> <68fea449-6478-3d6d-addf-79925ca62931@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from mga09.intel.com ([134.134.136.24]:44064 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754958AbeBAUkt (ORCPT ); Thu, 1 Feb 2018 15:40:49 -0500 In-Reply-To: <68fea449-6478-3d6d-addf-79925ca62931@codeaurora.org> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Sinan Kaya , dmaengine , "Rafael J . Wysocki" , linux-acpi@vger.kernel.org Cc: Sakari Ailus , Vinod Koul On Thu, 2018-02-01 at 15:32 -0500, Sinan Kaya wrote: > On 2/1/2018 3:20 PM, Andy Shevchenko wrote: > > When __acpi_match_device() is called it would be possible to have > > ACPI ID table a MULL pointer. To avoid potential dereference, > > NULL Thanks, will fix later. > Why not bail out here immediately if ids is null? Because of the code which wasn't in context of this patch. See also patch 1 in the series. It's about how acpi_driver_match_device() uses it. -- Andy Shevchenko Intel Finland Oy