From: Takashi Iwai <tiwai@suse.de>
To: syzbot <syzbot+803e0047ac3a3096bb4f@syzkaller.appspotmail.com>
Cc: <alsa-devel@alsa-project.org>, <syzkaller-bugs@googlegroups.com>,
<perex@perex.cz>, <o-takashi@sakamocchi.jp>,
<linux-kernel@vger.kernel.org>
Subject: Re: WARNING in snd_pcm_hw_params
Date: Mon, 09 Apr 2018 17:18:05 +0200 [thread overview]
Message-ID: <s5hbmesflxu.wl-tiwai@suse.de> (raw)
In-Reply-To: <001a113fe6c005d8ac056922c4c3@google.com>
On Fri, 06 Apr 2018 02:02:02 +0200,
syzbot wrote:
>
> WARNING: CPU: 0 PID: 4468 at sound/core/pcm_native.c:620
> snd_pcm_hw_params_choose sound/core/pcm_native.c:620 [inline]
This is a WARN_ON() to catch the inconsistent hw_params call.
This shouldn't happen in theory, but the reality looks weirder.
The necessary "fix" is just to get rid of snd_BUG_ON(), but still
wonder which condition it hits. If it's an empty parameter, the
previous snd_pcm_hw_refine() should have caught and returned the error
beforehand...
In anyway this can't be a real crash, let's remove the warning to stop
the chorus of syzbot birds.
thanks,
Takashi
-- 8< --
From: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH] ALSA: pcm: Remove WARN_ON() at snd_pcm_hw_params() error
snd_pcm_hw_params() may hit WARN_ON() when an inconsistent parameter
set is passed. Although this should have been caught by the former
snd_pcm_hw_refine() and returned the error, syzkaller succeeded to
pass through and hit the WARN_ON(), which in turn made it panic
unnecessarily.
For reducing this kind of noise, let's drop snd_BUG_ON() check.
Reported-by: syzbot+803e0047ac3a3096bb4f@syzkaller.appspotmail.com
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
sound/core/pcm_native.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/core/pcm_native.c b/sound/core/pcm_native.c
index b84554893fab..35ffccea94c3 100644
--- a/sound/core/pcm_native.c
+++ b/sound/core/pcm_native.c
@@ -617,7 +617,7 @@ static int snd_pcm_hw_params_choose(struct snd_pcm_substream *pcm,
changed = snd_pcm_hw_param_first(pcm, params, *v, NULL);
else
changed = snd_pcm_hw_param_last(pcm, params, *v, NULL);
- if (snd_BUG_ON(changed < 0))
+ if (changed < 0)
return changed;
if (changed == 0)
continue;
--
2.16.3
next prev parent reply other threads:[~2018-04-09 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 0:02 WARNING in snd_pcm_hw_params syzbot
2018-04-09 15:18 ` Takashi Iwai [this message]
2018-04-09 15:25 ` Dmitry Vyukov
2018-04-09 15:33 ` Takashi Iwai
2018-04-09 15:44 ` Takashi Iwai
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=s5hbmesflxu.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=perex@perex.cz \
--cc=syzbot+803e0047ac3a3096bb4f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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