Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1448123ybt; Sun, 14 Jun 2020 23:57:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwkAon59r+0gXarHJ5tiIhS0zZaOBJkOB22E+DWimZMAPZuZN7/7oa5Dr4geahhm2yOOVYK X-Received: by 2002:aa7:d952:: with SMTP id l18mr22136115eds.151.1592204221047; Sun, 14 Jun 2020 23:57:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592204221; cv=none; d=google.com; s=arc-20160816; b=ojouoLT2faLRw/+p6R2ayV0Gk9CsDVxBms9LFrc3+yOhzFxc8842RsYbHZZc2EyNXk JWFhSSwKnIQm7dbVpOOnlCqQ7/O75wrGzirnsiCyKtCOuV39LEwFnU328kVRhkI8fbWk W8Zh1P+9Lnb6rNA3Xb0l/Yk1JE6+yGIjLPfezl4r7hDHPjK/z/Mga2FhYN05RwVEag4+ XK46kb+YKVrXiCpEl+cDGWbwqCB00NIV0WAAISfPibcunBfqDyJikN4zrbeJArWybd66 +dRUqiokf6Sd+f+Wwqd7+5/E7k4GgB9KlGqsc9GwL01MsPV45c15abIFAKx6aez0TBk/ myLg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=FzpcJt0ssUXnqR5Y4j7PN2JBfi8J4vbayimjMBYGH8k=; b=t3wMnOK6NgVCXE25UgLeYDnbcC5PuflyEiFVtHQhKv9X7Njul8KP46HEhcbasqlWiN wwsswPm8FOcREBYkFINsiS+2JbzKLagl6F9IKYiRU7ZEiMt8BtCCAJ4pR/4ltBWOlCAF 39B6cEYCMWW0V9XHZuoGmhJJ/yovH2Rs8oOMOOwB2YI4HeYM0gk1fWpVHk8sQ9MjeaxK 2F4ULoVoQiQFh2C/+VCex+3k0cTtwl58Z5ZBkoi6MGFc0kx2RjV3HzB55QgtjEvvblEl 2n16YT8YriW25W8NOoSsG+40E8R9s3xPXTC5QLGQ9A4HhPRkDM5/g11nUYl1054uk+Gf bmQA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e2si8025435edv.101.2020.06.14.23.56.39; Sun, 14 Jun 2020 23:57:01 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728417AbgFOGy6 (ORCPT + 99 others); Mon, 15 Jun 2020 02:54:58 -0400 Received: from verein.lst.de ([213.95.11.211]:59830 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726111AbgFOGy6 (ORCPT ); Mon, 15 Jun 2020 02:54:58 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 82E9968B02; Mon, 15 Jun 2020 08:54:55 +0200 (CEST) Date: Mon, 15 Jun 2020 08:54:55 +0200 From: Christoph Hellwig To: David Rientjes Cc: Christoph Hellwig , Thomas Lendacky , Brijesh Singh , Marek Szyprowski , Robin Murphy , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [patch for-5.8 1/4] dma-direct: always align allocation size in dma_direct_alloc_pages() Message-ID: <20200615065455.GA21248@lst.de> References: 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) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 11, 2020 at 12:20:28PM -0700, David Rientjes wrote: > dma_alloc_contiguous() does size >> PAGE_SHIFT and set_memory_decrypted() > works at page granularity. It's necessary to page align the allocation > size in dma_direct_alloc_pages() for consistent behavior. > > This also fixes an issue when arch_dma_prep_coherent() is called on an > unaligned allocation size for dma_alloc_need_uncached() when > CONFIG_DMA_DIRECT_REMAP is disabled but CONFIG_ARCH_HAS_DMA_SET_UNCACHED > is enabled. > > Cc: stable@vger.kernel.org > Signed-off-by: David Rientjes > --- > kernel/dma/direct.c | 17 ++++++++++------- > 1 file changed, 10 insertions(+), 7 deletions(-) > > diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c > --- a/kernel/dma/direct.c > +++ b/kernel/dma/direct.c > @@ -112,11 +112,12 @@ static inline bool dma_should_free_from_pool(struct device *dev, > struct page *__dma_direct_alloc_pages(struct device *dev, size_t size, > gfp_t gfp, unsigned long attrs) > { > - size_t alloc_size = PAGE_ALIGN(size); > int node = dev_to_node(dev); > struct page *page = NULL; > u64 phys_limit; > > + VM_BUG_ON(!PAGE_ALIGNED(size)); This really should be a WARN_ON_ONCE, but I've fixed this up before applying. I've also added a prep patch to mark __dma_direct_alloc_pages static as part of auditing for other callers.