From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751886AbeDIM7p (ORCPT <rfc822;w@1wt.eu>);
        Mon, 9 Apr 2018 08:59:45 -0400
Received: from mx2.suse.de ([195.135.220.15]:41429 "EHLO mx2.suse.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1750982AbeDIM7n (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 9 Apr 2018 08:59:43 -0400
Date: Mon, 09 Apr 2018 14:59:38 +0200
Message-ID: <s5h7epgh6x1.wl-tiwai@suse.de>
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
In-Reply-To: <201804082226.AGF09317.OtLQHOFMJFSFVO@I-love.SAKURA.ne.jp>
References: <00000000000014ed1e056928bb60@google.com>
        <84930b72-d55d-90a2-e0df-29279545aa25@I-love.SAKURA.ne.jp>
        <CACT4Y+a_Sm6AAK1x1o5p7MQxb+EO3ZDxhNorv98UB4kbWfRscw@mail.gmail.com>
        <201804082226.AGF09317.OtLQHOFMJFSFVO@I-love.SAKURA.ne.jp>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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