linux-kernel - [BUG] haswell: a possible sleep-in-atomic bug in hsw_irq

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <aa7a630d-f3ec-a11d-7ec0-1350c6dea095@gmail.com>
Date:   Tue, 12 Dec 2017 22:19:42 +0800
From:   Jia-Ju Bai <baijiaju1990@...il.com>
To:     yang.jie@...ux.intel.com, lgirdwood@...il.com, broonie@...nel.org,
        perex@...ex.cz, tiwai@...e.com
Cc:     alsa-devel@...a-project.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [BUG] haswell: a possible sleep-in-atomic bug in hsw_irq_thread

According to sound/soc/intel/haswell/sst-haswell-ipc.c, the driver may 
sleep under a spinlock.
The function call path is:
hsw_irq_thread (acquire the spinlock)
   hsw_process_notification
     hsw_log_message
       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.


Thanks,
Jia-Ju Bai