Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 09 Jun 2020 13:02:46 +0200
Message-ID: <s5h8sgwijs9.wl-tiwai@suse.de>
From:   Takashi Iwai <tiwai@suse.de>
To:     Christoph Hellwig <hch@lst.de>
Cc:     David Rientjes <rientjes@google.com>,
        "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>,
        alsa-devel@alsa-project.org, bp@alien8.de, hch@infradead.org,
        hpa@zytor.com, linux-kernel@vger.kernel.org, mingo@redhat.com,
        Pavel Machek <pavel@ucw.cz>, perex@perex.cz,
        tglx@linutronix.de, tiwai@suse.com, x86@kernel.org
Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash
In-Reply-To: <s5hh7vkio0n.wl-tiwai@suse.de>
References: <20200520111136.GA3802@amd>
        <1591545088.74ii116nf2.none@localhost>
        <20200608061950.GA17476@lst.de>
        <1591624340.z01ejtod28.none@localhost>
        <alpine.DEB.2.22.394.2006081928070.148886@chino.kir.corp.google.com>
        <20200609054306.GA9606@lst.de>
        <s5hsgf4irzt.wl-tiwai@suse.de>
        <20200609084305.GA21671@lst.de>
        <s5hlfkwip1h.wl-tiwai@suse.de>
        <20200609091727.GA23814@lst.de>
        <s5hh7vkio0n.wl-tiwai@suse.de>
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
Precedence: bulk

On Tue, 09 Jun 2020 11:31:20 +0200,
Takashi Iwai wrote:
> 
> On Tue, 09 Jun 2020 11:17:27 +0200,
> Christoph Hellwig wrote:
> > 
> > On Tue, Jun 09, 2020 at 11:09:14AM +0200, Takashi Iwai wrote:
> > > On Tue, 09 Jun 2020 10:43:05 +0200,
> > > Christoph Hellwig wrote:
> > > > 
> > > > On Tue, Jun 09, 2020 at 10:05:26AM +0200, Takashi Iwai wrote:
> > > > > > >From the disassembly it seems like a vmalloc allocation is NULL, which
> > > > > > seems really weird as this patch shouldn't make a difference for them,
> > > > > > and I also only see a single places that allocates the field, and that
> > > > > > checks for an allocation failure.  But the sound code is a little
> > > > > > hard to unwind sometimes.
> > > > > 
> > > > > It's not clear which sound device being affected, but if it's
> > > > > HD-audio on x86, runtime->dma_area points to a vmapped buffer from
> > > > > SG-pages allocated by dma_alloc_coherent().
> > > > > 
> > > > > OTOH, if it's a USB-audio, runtime->dma_area is a buffer by
> > > > > vmalloc().
> > > > 
> > > > Err, you can't just vmap a buffer returned from dma_alloc_coherent,
> > > > dma_alloc_coherent returns values are opaque and can't be used
> > > > for virt_to_page.  Whatever that code did has already been broken
> > > > per the DMA API contract and on many architectures and just happend
> > > > to work on x86 by accident.
> > > 
> > > Hmm, that's bad.
> > > 
> > > How would be a proper way to get the virtually mapped SG-buffer pages
> > > with coherent memory?  (Also allowing user-space mmap, too)
> > 
> > dma_mmap_coherent / dma_mmap_attrs for userspace.  We don't really
> > have a good way for kernel space mappings.
> 
> And that's the missing piece right now...  :-<

BTW, this kind of usage is not specific to sound, but also V4L also
does vmap() over SG pages from dma_alloc_coherent().  It seems done
only on selected devices, though.


Takashi