Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754915Ab2K2Xqm (ORCPT ); Thu, 29 Nov 2012 18:46:42 -0500 Received: from hydra.sisk.pl ([212.160.235.94]:36543 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753778Ab2K2Xqj (ORCPT ); Thu, 29 Nov 2012 18:46:39 -0500 From: "Rafael J. Wysocki" To: Shuah Khan Cc: ACPI Devel Maling List , LKML , Linux PM list , Zdenek Kabelac Subject: Re: [PATCH] ACPI / PNP: Do not crash due to stale pointer use during system resume Date: Fri, 30 Nov 2012 00:51:25 +0100 Message-ID: <28227702.6DTxM78Dej@vostro.rjw.lan> User-Agent: KMail/4.9.3 (Linux/3.7.0-rc7; KDE/4.9.3; x86_64; ; ) In-Reply-To: References: <1829835.4TBEQGhjkq@vostro.rjw.lan> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1991 Lines: 44 On Thursday, November 29, 2012 04:25:20 PM Shuah Khan wrote: > On Thu, Nov 29, 2012 at 4:10 PM, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > During resume from system suspend the 'data' field of > > struct pnp_dev in pnpacpi_set_resources() may be a stale pointer, > > due to removal of the associated ACPI device node object in the > > previous suspend-resume cycle. This happens, for example, if a > > dockable machine is booted in the docking station and then suspended > > and resumed and suspended again. If that happens, > > pnpacpi_build_resource_template() called from pnpacpi_set_resources() > > attempts to use that pointer and crashes. > > > > However, pnpacpi_set_resources() actually checks the device's ACPI > > handle, attempts to find the ACPI device node object attached to it > > and returns an error code if that fails, so in fact it knows what the > > correct value of dev->data should be. Use this observation to update > > dev->data with the correct value if necessary and dump a call trace > > if that's the case (once). > > > > We still need to fix the root cause of this issue, but preventing > > systems from crashing because of it is an improvement too. > > > > Reported-and-tested-by: Zdenek Kabelac > > References: https://bugzilla.kernel.org/show_bug.cgi?id=51071 > > Signed-off-by: Rafael J. Wysocki > > Any reason why this shouldn't go into stable releases? Yes, it can go to -stable. This is just a patch, not a git commit. I can still add the "stable" tag to it when it goes to git. :-) Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/