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 X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1CAA8C433DB for ; Tue, 9 Feb 2021 15:52:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DC9BD64E70 for ; Tue, 9 Feb 2021 15:52:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232627AbhBIPvr (ORCPT ); Tue, 9 Feb 2021 10:51:47 -0500 Received: from verein.lst.de ([213.95.11.211]:47186 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232384AbhBIPvm (ORCPT ); Tue, 9 Feb 2021 10:51:42 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id 9E5D467373; Tue, 9 Feb 2021 16:50:58 +0100 (CET) Date: Tue, 9 Feb 2021 16:50:58 +0100 From: Christoph Hellwig To: Robin Murphy Cc: Sumit Garg , Christoph Hellwig , Greg KH , obayashi.yoshimasa@socionext.com, m.szyprowski@samsung.com, iommu@lists.linux-foundation.org, Linux Kernel Mailing List , stable , Daniel Thompson Subject: Re: DMA direct mapping fix for 5.4 and earlier stable branches Message-ID: <20210209155058.GA8912@lst.de> References: <27bbe35deacb4ca49f31307f4ed551b5@SOC-EX02V.e01.socionext.com> <20210209093642.GA1006@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 Tue, Feb 09, 2021 at 12:45:11PM +0000, Robin Murphy wrote: > It's not a bug, it's a fundamental design failure. dma_get_sgtable() has > only ever sort-of-worked for DMA buffers that come from CMA or regular page > allocations. In particular, a "no-map" DMA pool is not backed by kernel > memory, so does not have any corresponding page structs, so it's impossible > to generate a *valid* scatterlist to represent memory from that pool, > regardless of what you might get away with provided you don't poke too hard > at it. > > It is not a good API... Yes, I don't think anyone should add new users of the API. That being said the commit he is trying to backport fixes a bug in the implementation that at least in theory could also affect in-tree drivers.