Re: [BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

2018-10-10 Thread Jia-Ju Bai
On 2018/10/9 17:07, Lee Jones wrote: On Mon, 17 Sep 2018, Jia-Ju Bai wrote: On 2018/9/17 9:03, Lee Jones wrote: 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 d

Re: [BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

2018-10-09 Thread Lee Jones
On Mon, 17 Sep 2018, Jia-Ju Bai wrote: > > > On 2018/9/17 9:03, Lee Jones wrote: > > 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 > > > d

Re: [BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

2018-09-16 Thread Jia-Ju Bai
On 2018/9/17 9:03, Lee Jones wrote: 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 ha

Re: [BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

2018-09-16 Thread Lee Jones
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_n

[BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

2018-09-15 Thread Jia-Ju Bai
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_neste