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=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham 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 A0096C10F0E for ; Sun, 7 Apr 2019 06:59:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6DC9021738 for ; Sun, 7 Apr 2019 06:59:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726366AbfDGG7h (ORCPT ); Sun, 7 Apr 2019 02:59:37 -0400 Received: from verein.lst.de ([213.95.11.211]:35788 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725996AbfDGG7g (ORCPT ); Sun, 7 Apr 2019 02:59:36 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id B7D2A67329; Sun, 7 Apr 2019 08:59:23 +0200 (CEST) Date: Sun, 7 Apr 2019 08:59:23 +0200 From: Christoph Hellwig To: Robin Murphy Cc: Christoph Hellwig , Joerg Roedel , Catalin Marinas , Will Deacon , Tom Lendacky , iommu@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 02/21] arm64/iommu: improve mmap bounds checking Message-ID: <20190407065923.GA9086@lst.de> References: <20190327080448.5500-1-hch@lst.de> <20190327080448.5500-3-hch@lst.de> <3629087c-a8cb-d66e-840b-cfee125bdf4c@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3629087c-a8cb-d66e-840b-cfee125bdf4c@arm.com> 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 Fri, Apr 05, 2019 at 06:30:52PM +0100, Robin Murphy wrote: > On 27/03/2019 08:04, Christoph Hellwig wrote: >> The nr_pages checks should be done for all mmap requests, not just those >> using remap_pfn_range. > > Hmm, the logic in iommu_dma_mmap() inherently returns an error for the "off > >= nr_pages" case already. It's also supposed to be robust against the > "vma_pages(vma) > nr_pages - off" condition, although by making the partial > mapping and treating it as a success, rather than doing nothing and > returning an error. What's the exact motivation here? Have one error check at the front of the function that is identical to the mmap checks in the other dma_map_ops instances so that: a) we get the same error behavior for partial requests everywhere b) we can lift these checks into common code in the next round.