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=-3.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 D97BCC388F2 for ; Fri, 6 Nov 2020 08:35:45 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6723F21707 for ; Fri, 6 Nov 2020 08:35:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="oK9TeFz5" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6723F21707 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ziepe.ca Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 5AECC6EE1B; Fri, 6 Nov 2020 08:35:05 +0000 (UTC) Received: from mail-qt1-x843.google.com (mail-qt1-x843.google.com [IPv6:2607:f8b0:4864:20::843]) by gabe.freedesktop.org (Postfix) with ESMTPS id AF8576E87A for ; Fri, 6 Nov 2020 00:08:53 +0000 (UTC) Received: by mail-qt1-x843.google.com with SMTP id i7so2511746qti.6 for ; Thu, 05 Nov 2020 16:08:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=78w6rDG7nYDKrfBll/YwQv2rf14yq6PqmoJY+j3GkfA=; b=oK9TeFz5Y2+oPNpu4vAkXNsgSeyj4dFFNDSfIlFeLkjR2+rMKoWVaHhcD1jWUep1iU O0kqqjjRr96bXm05qChk2aYsIt2gzPYEGmaBvBoI6kqYQ445yCwD5P7a5an/upxNV1de BKiubDGb77zjk6a2drr0W4dR7wKqarRg76H2mZLca//OYydPtrnht3n194Lu5XRE+pSF cdrnb9BmXRzhDsBMsSqcN2OjLyEVvWpM6dBJ6rhJ1j86CZ8X5ZRe5aaFeagn1H3fBe0a /5l8lRf/E4gMmWkyN1ZStf3HRZMEYUjJNBU4Me3bVqYrFht7zNigDLO5YnE9KGOBubHG u2Aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=78w6rDG7nYDKrfBll/YwQv2rf14yq6PqmoJY+j3GkfA=; b=Cdd0iJMnibbOZgpEYFcS9E53IAP844dZQyz57uzFYVPlFhgviyF/Lv871JDVfR+fhv JBBnJdHVnS2gTBEQXCPOhSVXC/SE81vGzhyU0ODxV1sCVYJ649Q9VV6Nfv5pHJBh8HSM bkHiOzcjCgjsJI2d2cx+pdaeYJtHI3t8cp/9QzbX/UaiFXrxY0XN00V/Wc5P/vaaS0mE FOCZA7KdAyirrk39KtNQTig+vlNSt5bKtQDkY3IqkFDZpkNElGjBvp/agRAAo9kdpB9g ijX80GH5godzHKYW7Mv56P2jn5H99Nz1PIrM+GkV5nExyUKrEAgIk0xKGNRMrKJPllId KLjQ== X-Gm-Message-State: AOAM532d+7QDFdUADtsfsMGsWzBCwsZfZj7AVyN84boNsNX2+RQjvifN 5zIuRwXRHBZVYtCF0LEcDTyhMA== X-Google-Smtp-Source: ABdhPJy+gPuYXCviMw5rApuKiLeVIUfcEAbxylsl1vWQxlZWJBZzVkUWspauEUbEmOu6qlX4ZM956A== X-Received: by 2002:aed:2843:: with SMTP id r61mr4611334qtd.166.1604621332628; Thu, 05 Nov 2020 16:08:52 -0800 (PST) Received: from ziepe.ca (hlfxns017vw-156-34-48-30.dhcp-dynamic.fibreop.ns.bellaliant.net. [156.34.48.30]) by smtp.gmail.com with ESMTPSA id d20sm2167345qkj.49.2020.11.05.16.08.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 05 Nov 2020 16:08:51 -0800 (PST) Received: from jgg by mlx with local (Exim 4.94) (envelope-from ) id 1kapJD-000Yst-1D; Thu, 05 Nov 2020 20:08:51 -0400 Date: Thu, 5 Nov 2020 20:08:51 -0400 From: Jason Gunthorpe To: Jianxin Xiong Subject: Re: [PATCH v8 1/5] RDMA/umem: Support importing dma-buf as user memory region Message-ID: <20201106000851.GK36674@ziepe.ca> References: <1604616489-69267-1-git-send-email-jianxin.xiong@intel.com> <1604616489-69267-2-git-send-email-jianxin.xiong@intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1604616489-69267-2-git-send-email-jianxin.xiong@intel.com> X-Mailman-Approved-At: Fri, 06 Nov 2020 08:34:42 +0000 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Leon Romanovsky , linux-rdma@vger.kernel.org, dri-devel@lists.freedesktop.org, Doug Ledford , Daniel Vetter , Christian Koenig Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Thu, Nov 05, 2020 at 02:48:05PM -0800, Jianxin Xiong wrote: > + /* modify the sgl in-place to match umem address and length */ > + > + start = ALIGN_DOWN(umem_dmabuf->umem.address, PAGE_SIZE); > + end = ALIGN(umem_dmabuf->umem.address + umem_dmabuf->umem.length, > + PAGE_SIZE); > + cur = 0; > + nmap = 0; > + for_each_sgtable_dma_sg(sgt, sg, i) { > + if (cur >= end) > + break; > + if (cur + sg_dma_len(sg) <= start) { > + cur += sg_dma_len(sg); > + continue; > + } This seems like a strange way to compute interesections if (cur <= start && start < cur + sg_dma_len(sg)) > + if (cur <= start) { > + unsigned long offset = start - cur; > + > + umem_dmabuf->first_sg = sg; > + umem_dmabuf->first_sg_offset = offset; > + sg_dma_address(sg) += offset; > + sg_dma_len(sg) -= offset; > + if (&sg_dma_len(sg) != &sg->length) > + sg->length -= offset; We don't need to adjust sg->length, only dma_len, so no reason for this surprising if. > + cur += offset; > + } > + if (cur + sg_dma_len(sg) >= end) { Same logic here > + unsigned long trim = cur + sg_dma_len(sg) - end; > + > + umem_dmabuf->last_sg = sg; > + umem_dmabuf->last_sg_trim = trim; > + sg_dma_len(sg) -= trim; > + if (&sg_dma_len(sg) != &sg->length) > + sg->length -= trim; break, things are done here > + } > + cur += sg_dma_len(sg); > + nmap++; > + } > + > + umem_dmabuf->umem.sg_head.sgl = umem_dmabuf->first_sg; > + umem_dmabuf->umem.sg_head.nents = nmap; > + umem_dmabuf->umem.nmap = nmap; > + umem_dmabuf->sgt = sgt; > + > + page_size = ib_umem_find_best_pgsz(&umem_dmabuf->umem, PAGE_SIZE, > + umem_dmabuf->umem.iova); > + > + if (WARN_ON(cur != end || page_size != PAGE_SIZE)) { Looks like nothing prevents this warn on to tigger The user could specify a length that is beyond the dma buf, can the dma buf length be checked during get? Also page_size can be 0 because iova is not OK. iova should be checked for alignment during get as well: iova & (PAGE_SIZE-1) == umem->addr & (PAGE_SIZE-1) But yes, this is the right idea Jason _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel