Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751653AbdLLOUA (ORCPT ); Tue, 12 Dec 2017 09:20:00 -0500 Received: from mail-pf0-f196.google.com ([209.85.192.196]:39589 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750749AbdLLOTz (ORCPT ); Tue, 12 Dec 2017 09:19:55 -0500 X-Google-Smtp-Source: ACJfBouJufSxrQY9K1XuIe56rj0pYyKcC53ZGVDolnRLHJWkh7Q0kTIqlRMahk6y28jhedfhJV9/aw== To: yang.jie@linux.intel.com, lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz, tiwai@suse.com Cc: alsa-devel@alsa-project.org, Linux Kernel Mailing List From: Jia-Ju Bai Subject: [BUG] haswell: a possible sleep-in-atomic bug in hsw_irq_thread Message-ID: Date: Tue, 12 Dec 2017 22:19:42 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 411 Lines: 15 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