Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752044AbbEFNJr (ORCPT ); Wed, 6 May 2015 09:09:47 -0400 Received: from mail-oi0-f41.google.com ([209.85.218.41]:33094 "EHLO mail-oi0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751415AbbEFNJq (ORCPT ); Wed, 6 May 2015 09:09:46 -0400 MIME-Version: 1.0 In-Reply-To: <1429708841-31189-1-git-send-email-semen.protsenko@globallogic.com> References: <1429708841-31189-1-git-send-email-semen.protsenko@globallogic.com> Date: Wed, 6 May 2015 15:09:45 +0200 Message-ID: Subject: Re: [PATCH v2] gpio: max732x: Fix irq-events handler From: Linus Walleij To: Semen Protsenko Cc: Alexandre Courbot , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Grygorii Strashko 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: 1221 Lines: 33 On Wed, Apr 22, 2015 at 3:20 PM, Semen Protsenko wrote: > MAX732X clears all pending interrupts on I2C read (when interrupts > register is being read). Driver doesn't need to send any ACKs when > interrupt was handled. So replace handle_edge_irq() with > handle_simple_irq(). > > Using handle_edge_irq() (w/o .irq_ack callback set) may lead to NULL > pointer dereference in some cases. E.g. this was observed on > hibernation process: > > Unable to handle kernel NULL pointer dereference at virtual address 0 > Backtrace: > (handle_edge_irq) from (resend_irqs) > (resend_irqs) from (tasklet_action) > (tasklet_action) from (__do_softirq) > (__do_softirq) from (run_ksoftirqd) > (run_ksoftirqd) from (smpboot_thread_fn) > (smpboot_thread_fn) from (kthread) > (kthread) from (ret_from_fork) > > Signed-off-by: Semen Protsenko Patch applied with Grygorii's Review tag. Yours, Linus Walleij -- 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/