From: Takashi Iwai <tiwai@suse.de>
To: "Tetsuo Handa" <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: <dvyukov@google.com>, <alsa-devel@alsa-project.org>,
<syzkaller-bugs@googlegroups.com>, <mingo@kernel.org>,
<dan.carpenter@oracle.com>, <perex@perex.cz>,
<o-takashi@sakamocchi.jp>,
<syzbot+4f2016cf5185da7759dc@syzkaller.appspotmail.com>,
<linux-kernel@vger.kernel.org>, <viro@zeniv.linux.org.uk>
Subject: Re: INFO: rcu detected stall in io_playback_transfer
Date: Mon, 09 Apr 2018 14:59:38 +0200 [thread overview]
Message-ID: <s5h7epgh6x1.wl-tiwai@suse.de> (raw)
In-Reply-To: <201804082226.AGF09317.OtLQHOFMJFSFVO@I-love.SAKURA.ne.jp>
On Sun, 08 Apr 2018 15:26:21 +0200,
Tetsuo Handa wrote:
>
> Dmitry Vyukov wrote:
> > Takashi has already fixed this. See this thread:
> > https://groups.google.com/forum/#!searchin/syzkaller-bugs/%22INFO$3A$20rcu$20detected$20stall$20in$20snd_pcm_oss_write3$20(2)%22%7Csort:date/syzkaller-bugs/D2xWV7WTRDk/sCw_gImmCAAJ
>
> Yes, I noticed it just before I post this. But the reason I posted this anyway
> is that I feel that there is some other bug revealed by this reproducer.
> How can Takashi' patch explain my observation (with linux-next-20180406) ?
The bug is triggered by any buffer underrun of a PCM stream via OSS
emulation, so the condition can vary in any form. That is, if an app
doesn't give the enough amount in time, the PCM goes to XRUN state.
Then at closing, the driver tries to sync the pending data and hits
the bug.
Takashi
prev parent reply other threads:[~2018-04-09 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 7:09 syzbot
2018-04-08 12:58 ` Tetsuo Handa
2018-04-08 13:09 ` Dmitry Vyukov
2018-04-08 13:26 ` Tetsuo Handa
2018-04-09 12:59 ` Takashi Iwai [this message]
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=s5h7epgh6x1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=dan.carpenter@oracle.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=perex@perex.cz \
--cc=syzbot+4f2016cf5185da7759dc@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®