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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CC765C44532 for ; Tue, 21 Jul 2026 14:29:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=1soRxN4hiDcUXCxjs1PA7SeZGbKgmvbO8BnI4N1ZFe8=; b=iIXsbzTbXYhlB3ujqpePQlzRUX RpgdGV/TX8GQzEAZw6pftlOIWVMv1FASTD7nN8zget/hL3uFqgyd6cHUMEmDgr5sFTn+kiayjHxpB a3ZPvfvxJQjaXkP9xkf6xlCgn66kwOwkcRuvdxsykJKuLl6VtyvJO9djq7km3xPpf2rSXKigQSAGo xzr2Z6BEBZgCFskSxL1QGEoXY9aJiZGipVthaLFBqxbfa4612TFLfVrUmkQPgRINYwZEE+j2GyTpz b8gE9HGe4oHZk9NmK/SvLMROpPsqu8d3rvUFe4ART32Kkd1yDsACxlA20pDt2aFdNXRRr3guqIFwQ SBIeuL5A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wmBTP-00000009f3X-45vJ; Tue, 21 Jul 2026 14:29:31 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wmBTO-00000009f2x-0xIc for linux-arm-kernel@lists.infradead.org; Tue, 21 Jul 2026 14:29:30 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id 659DC403A9; Tue, 21 Jul 2026 14:29:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D7F491F000E9; Tue, 21 Jul 2026 14:29:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784644168; bh=1soRxN4hiDcUXCxjs1PA7SeZGbKgmvbO8BnI4N1ZFe8=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=Z6Y53ElnThJz/QmjNlBI90Yu7tbBuCvQU60QJ4DbRT5TXWdL7w3KuZzUdsCjKtoL/ 71ZaLms1OHJ+aJGCsLyIDPyM7gGELMJkUoUEEKbfKXlEoG+CcCrbpbAg43lxbizIqO yXWwFnJWX4Ru3nShSGjh7T+m6/UYy1o50khWKiQF8rvhylkfkDK/1Kki7v+jYxq5aI gO/tbH5nUZoF4TeZXpFnsJTsnW6/YStJLzyv9G5e7g6RhjKNbNUznJMyPNGHNkYE0+ ZTUeuFNaF4ExWmaFhhdtjEOn8TaeQv52hbnyhHF4K8laJqqVGxQz+/SpgRyB1FtKpa iraCr9pMDtqtA== Date: Tue, 21 Jul 2026 17:29:21 +0300 From: Leon Romanovsky To: "Aneesh Kumar K.V" Cc: iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev, Robin Murphy , Marek Szyprowski , Will Deacon , Marc Zyngier , Steven Price , Suzuki K Poulose , Catalin Marinas , Jiri Pirko , Jason Gunthorpe , Mostafa Saleh , Petr Tesarik , Alexey Kardashevskiy , Dan Williams , Xu Yilun , linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, Madhavan Srinivasan , Michael Ellerman , Nicholas Piggin , "Christophe Leroy (CS GROUP)" , Alexander Gordeev , Gerald Schaefer , Heiko Carstens , Vasily Gorbik , Christian Borntraeger , Sven Schnelle , x86@kernel.org, stable@vger.kernel.org, Michael Kelley , Jason Gunthorpe Subject: Re: [PATCH v8 01/23] dma-direct: return struct page from dma_direct_alloc_from_pool() Message-ID: <20260721142921.GN110966@unreal> References: <20260717180442.110954-1-aneesh.kumar@kernel.org> <20260717180442.110954-2-aneesh.kumar@kernel.org> <20260721115456.GI110966@unreal> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Jul 21, 2026 at 07:50:10PM +0530, Aneesh Kumar K.V wrote: > Leon Romanovsky writes: > > > On Fri, Jul 17, 2026 at 11:34:19PM +0530, Aneesh Kumar K.V (Arm) wrote: > >> Commit 5b138c534fda ("dma-direct: factor out a dma_direct_alloc_from_pool > >> helper") changed dma_direct_alloc_from_pool() to return the CPU address > >> from dma_alloc_from_pool(). That fits dma_direct_alloc(), but > >> dma_direct_alloc_pages() also uses the helper and expects a struct page *. > >> > >> Fix this by making dma_direct_alloc_from_pool() return the struct page * > >> again, and pass the CPU address back through an out-parameter for the > >> dma_direct_alloc() caller. > >> > >> Fixes: 5b138c534fda ("dma-direct: factor out a dma_direct_alloc_from_pool helper") > >> Cc: stable@vger.kernel.org > >> Tested-by: Michael Kelley > >> Tested-by: Mostafa Saleh > >> Reviewed-by: Jason Gunthorpe > >> Signed-off-by: Aneesh Kumar K.V (Arm) > >> --- > >> kernel/dma/direct.c | 18 ++++++++++-------- > >> 1 file changed, 10 insertions(+), 8 deletions(-) > >> > >> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c > >> index d8219efe3273..363d984d90e7 100644 > >> --- a/kernel/dma/direct.c > >> +++ b/kernel/dma/direct.c > >> @@ -164,22 +164,21 @@ static bool dma_direct_use_pool(struct device *dev, gfp_t gfp) > >> return !gfpflags_allow_blocking(gfp) && !is_swiotlb_for_alloc(dev); > >> } > >> > >> -static void *dma_direct_alloc_from_pool(struct device *dev, size_t size, > >> - dma_addr_t *dma_handle, gfp_t gfp) > >> +static struct page *dma_direct_alloc_from_pool(struct device *dev, size_t size, > >> + dma_addr_t *dma_handle, void **cpu_addr, gfp_t gfp) > >> { > >> struct page *page; > >> u64 phys_limit; > >> - void *ret; > >> > >> if (WARN_ON_ONCE(!IS_ENABLED(CONFIG_DMA_COHERENT_POOL))) > >> return NULL; > >> > >> gfp |= dma_direct_optimal_gfp_mask(dev, &phys_limit); > >> - page = dma_alloc_from_pool(dev, size, &ret, gfp, dma_coherent_ok); > >> + page = dma_alloc_from_pool(dev, size, cpu_addr, gfp, dma_coherent_ok); > >> if (!page) > >> return NULL; > >> *dma_handle = phys_to_dma_direct(dev, page_to_phys(page)); > >> - return ret; > >> + return page; > >> } > >> > >> static void *dma_direct_alloc_no_mapping(struct device *dev, size_t size, > >> @@ -247,8 +246,11 @@ void *dma_direct_alloc(struct device *dev, size_t size, > >> * the atomic pools instead if we aren't allowed block. > >> */ > >> if ((remap || force_dma_unencrypted(dev)) && > >> - dma_direct_use_pool(dev, gfp)) > >> - return dma_direct_alloc_from_pool(dev, size, dma_handle, gfp); > >> + dma_direct_use_pool(dev, gfp)) { > >> + page = dma_direct_alloc_from_pool(dev, size, dma_handle, > >> + &ret, gfp); > >> + return page ? ret : NULL; > > > > Sorry for joining the discussion late, but the line above caught my > > attention. > > > > Why do we need both ret and page? We can derive cpu_addr from page and > > vice versa. Do we really need the &ret parameter? Or, more generally, do > > we really need "struct page *"? > > > > static struct page *__dma_alloc_from_pool(struct device *dev, size_t size, > > struct gen_pool *pool, void **cpu_addr, > > bool (*phys_addr_ok)(struct device *, phys_addr_t, size_t)) > > { > > ... > > *cpu_addr = (void *)addr; > > memset(*cpu_addr, 0, size); > > return pfn_to_page(__phys_to_pfn(phys)); > > } > > > > Why > > > > With CONFIG_DMA_DIRECT_REMAP the cpu_addr can be different from > page_address. Can you please point to the code there it can happen? __dma_alloc_from_pool() has direct connection between physical address and struct page. Thanks > > -aneesh >