On Mon, Mar 31, 2014 at 2:16 PM, Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> wrote: > Commit aa92b6f689ac (gpio / ACPI: Allocate ACPI specific data directly in > acpi_gpiochip_add()) moved ACPI handle checking to acpi_gpiochip_add() but > forgot to check whether chip->dev is NULL before dereferencing it. > > Since chip->dev pointer is optional we can end up with crash like following: Sorry for taking so long before getting to it, patch applied for fixes. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] gpio / ACPI: Don't crash on NULL chip->dev
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] gpio / ACPI: Don't crash on NULL chip->dev
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Thu, 10 Apr 2014 18:06:01 +0200
- In-reply-to: <1396268209-19108-1-git-send-email-mika.westerberg@linux.intel.com>
- References:
- [PATCH] gpio / ACPI: Don't crash on NULL chip->dev
- From: Mika Westerberg
- [PATCH] gpio / ACPI: Don't crash on NULL chip->dev
- Prev by Date: Re: [PATCH 1/2] ARM: SAMSUNG: remove gpio flags in dev-backlight
- Next by Date: Re: [PATCH] gpio / ACPI: Prevent potential wrap of GPIO value on OpRegion read
- Previous by thread: Re: [PATCH] gpio / ACPI: Don't crash on NULL chip->dev
- Next by thread: [PATCH] gpio / ACPI: Prevent potential wrap of GPIO value on OpRegion read
- Index(es):
 |