From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8FB8FC4167B for ; Fri, 16 Dec 2022 12:15:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230255AbiLPMP3 (ORCPT ); Fri, 16 Dec 2022 07:15:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56432 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229665AbiLPMP0 (ORCPT ); Fri, 16 Dec 2022 07:15:26 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B51762FBC4 for ; Fri, 16 Dec 2022 04:15:25 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 8637667373; Fri, 16 Dec 2022 13:15:20 +0100 (CET) Date: Fri, 16 Dec 2022 13:15:19 +0100 From: Christoph Hellwig To: Robin Murphy Cc: Christoph Hellwig , Mikhail Gavrilov , Takashi Iwai , alsa-devel@alsa-project.org, m.szyprowski@samsung.com, Linux List Kernel Mailing , iommu@lists.linux.dev Subject: Re: [6.2][regression] after commit ffcb754584603adf7039d7972564fbf6febdc542 all sound devices disappeared (due BUG at mm/page_alloc.c:3592!) Message-ID: <20221216121519.GA5710@lst.de> References: <20221216064645.GA24446@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 16, 2022 at 11:40:57AM +0000, Robin Murphy wrote: > On 2022-12-16 06:46, Christoph Hellwig wrote: >> Ok, it seems like the sound noncontig alloc code that I already >> commented on as potentially bogus GFP_GOMP mapping trips this. I think >> for now the right thing would be to revert the hunk in dma-iommu.c >> (see patch below). The other thing to try would be to remove both >> uses GFP_COMP in sound/core/memalloc.c, which should have the same >> effect. > > Or we explicitly strip the flag in dma_alloc_noncontiguous() (and maybe > dma_alloc_pages() as well) for consistency with dma_alloc_attrs(). That > seems like it might be the most robust option. In the long run warning there and returning an error seems like the right thing to do, yes. I'm just a little worried doing this right now after the merge window.