linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jia-Ju Bai <baijiaju1990@163.com>
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 <linux-kernel@vger.kernel.org>
Subject: [BUG] haswell: A possible sleep-in-atomic bug in hsw_irq_thread
Date: Sun, 8 Oct 2017 23:06:38 +0800	[thread overview]
Message-ID: <0ba5fa3a-1202-752f-e7f2-5d689b6a9e7c@163.com> (raw)

According to sst-haswell-ipc.c, the driver may sleep under a spinlock,
and the function call path is:
hsw_irq_thread (acquire the spinlock)
   hsw_process_notification
     hsw_log_message
       mutex_lock --> may sleep

This bug is found by my static analysis tool and my code review.


Thanks,
Jia-Ju Bai

             reply	other threads:[~2017-10-08 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 15:06 Jia-Ju Bai [this message]
2017-12-12 14:19 [BUG] haswell: a possible sleep-in-atomic bug in hsw_irq_thread Jia-Ju Bai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0ba5fa3a-1202-752f-e7f2-5d689b6a9e7c@163.com \
    --to=baijiaju1990@163.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=yang.jie@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).