Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 17 Sep 2018 02:03:40 +0100
From:   Lee Jones <lee.jones@linaro.org>
To:     Jia-Ju Bai <baijiaju1990@gmail.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in
 pcap_adc_irq()
Message-ID: <20180917010340.GA3900@dell>
References: <f83a444a-1943-6c8c-5cd4-88e2acb17fa6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <f83a444a-1943-6c8c-5cd4-88e2acb17fa6@gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sat, 15 Sep 2018, Jia-Ju Bai wrote:

> The driver may sleep in an interrupt handler.
> The function call paths (from bottom to top) in Linux-4.17 are:
> 
> [FUNC] mutex_lock_nested
> drivers/mfd/ezx-pcap.c, 272:
>     mutex_lock_nested in pcap_adc_irq (interrupt handler)
> 
> [FUNC] mutex_lock_nested
> drivers/mfd/ezx-pcap.c, 100:
>     mutex_lock_nested in ezx_pcap_read
> drivers/mfd/ezx-pcap.c, 281:
>     ezx_pcap_read in pcap_adc_irq (interrupt handler)
> 
> [FUNC] mutex_lock_nested
> drivers/mfd/ezx-pcap.c, 85:
>     mutex_lock_nested in ezx_pcap_write
> drivers/mfd/ezx-pcap.c, 285:
>     ezx_pcap_write in pcap_adc_irq (interrupt handler)
> 
> [FUNC] mutex_lock_nested
> drivers/mfd/ezx-pcap.c, 244:
>     mutex_lock_nested in pcap_adc_trigger
> drivers/mfd/ezx-pcap.c, 299:
>     pcap_adc_trigger in pcap_adc_irq (interrupt handler)
> 
> These bugs are found by my static analysis tool DSAC.

Not sure what you want me to do with this.

Do you have something in mind?

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog