lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20180205232514.GE46524@dtor-ws> Date: Mon, 5 Feb 2018 15:25:14 -0800 From: Dmitry Torokhov <dmitry.torokhov@...il.com> To: Jia-Ju Bai <baijiaju1990@...il.com>, Daniel Ribeiro <drwyrm@...il.com> Cc: ilya.muromec@...il.com, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [BUG] drivers/input/misc/pcap: a possible sleep-in-atomic bug in pcap_keys_handler On Tue, Dec 12, 2017 at 04:32:01PM +0800, Jia-Ju Bai wrote: > According to drivers/input/misc/pcap_keys.c, the kernel module may sleep in > the interrupt handler. > The function call path is: > pcap_keys_handler (interrupt handler) > ezx_pcap_read > mutex_lock --> may sleep > > I do not find a good way to fix it, so I only report. > This possible bug is found by my static analysis tool (DSAC) and checked by > my code review. Let's see if Daniel's email still work. I am not sure how it worked to begin with, given that we've been taking that mutex since very beginning, and pcap_isr_work() disables local interrupts... Thanks. -- Dmitry
Powered by blists - more mailing lists