Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp100381pxx; Tue, 27 Oct 2020 22:49:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy8Cw6b6RXbXLg/OrEO5gptko5OYX1NykupRMDk3RLKs5lJ02Bayj5U4J9SmRgToAqliJnB X-Received: by 2002:a17:907:429f:: with SMTP id ny23mr5723198ejb.150.1603864141697; Tue, 27 Oct 2020 22:49:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603864141; cv=none; d=google.com; s=arc-20160816; b=KRoryomE52Fc/j0wGG5qgBCb2tYLJYTW7l8TxFtIie73reuyRleLc7nN3mJ1qqEvNo EFmxaMvzigMCvGzMkTBq3WFbUfUMxrcCOhiI1UJ5+I7Z0xA5sEisfTgytZziSnRSSK57 ZbsEyqs/8PGlOMp5Dwy/hKy5pK0Q+MROx9Lj0+b81J0CdsQRg+pCLErir7feEfkM+VaJ HXqp7T+wQdeYTgi8LCuH+BM1Krpr/hETpNdzr+a6dHxvSwuuXmtF9P8MA0VNpmJLoSoW XuYJQx8A0su7jEK7wreM1OCEiSRlcDJ99+/rw8uSOaomuUrHW+VWF4m1H2UWK4rZyP8e kX0Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=BXV8gH7W9jsN+YBQpGTPpSWoYXVk1oikEFL0qNa5VBY=; b=G7zg2/uL5ZrnKsJOOdtVZIzm94zUc6zss184Wi0n/lGazTvIPEnqI9TgEI0aCOZv/a CPVJc3BDayOzv8QFxO3ahi/OqFGFNnkwir8sLyfRECgbKA2EGdUEzLXNtojKoPeK/P6o WY9MOwLlCmh52id1LFyDhzovslL+ala73Y6LEuRO/oydzmtLXERDeRrifh4uLlzNUNBF iwcAMqpWdWU8WjWhabGdiO3kLe5vHciTBCTfZJDb3aFrPGdoGoes3ouawmoOp+QivNQY Rgr7e0ps+UN8Mt6lQSTG6UzWNIfKwt3qd3m0GEPgpX5vfpv4+7ZL/4hxRDd/VDpuoUXW GYNQ== 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 v17si2583540eds.593.2020.10.27.22.48.24; Tue, 27 Oct 2020 22:49: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 S2508833AbgJ0ILJ (ORCPT + 99 others); Tue, 27 Oct 2020 04:11:09 -0400 Received: from verein.lst.de ([213.95.11.211]:37795 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2393441AbgJ0ILH (ORCPT ); Tue, 27 Oct 2020 04:11:07 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id C9A7967373; Tue, 27 Oct 2020 09:11:03 +0100 (CET) Date: Tue, 27 Oct 2020 09:11:03 +0100 From: "hch@lst.de" To: Parav Pandit Cc: Jakub Kicinski , syzbot , "christian.koenig@amd.com" , "dri-devel@lists.freedesktop.org" , "hch@lst.de" , "iommu@lists.linux-foundation.org" , "linaro-mm-sig-owner@lists.linaro.org" , "linaro-mm-sig@lists.linaro.org" , "linux-kernel@vger.kernel.org" , "linux-media@vger.kernel.org" , "m.szyprowski@samsung.com" , "netdev@vger.kernel.org" , "robin.murphy@arm.com" , "sumit.semwal@linaro.org" , "syzkaller-bugs@googlegroups.com" , "linux-rdma@vger.kernel.org" Subject: Re: WARNING in dma_map_page_attrs Message-ID: <20201027081103.GA22877@lst.de> References: <000000000000335adc05b23300f6@google.com> <000000000000a0f8a305b261fe4a@google.com> <20201024111516.59abc9ec@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> 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 Mon, Oct 26, 2020 at 05:23:48AM +0000, Parav Pandit wrote: > Hi Christoph, > > > From: Jakub Kicinski > > Sent: Saturday, October 24, 2020 11:45 PM > > > > CC: rdma, looks like rdma from the stack trace > > > > On Fri, 23 Oct 2020 20:07:17 -0700 syzbot wrote: > > > syzbot has found a reproducer for the following issue on: > > > > > > HEAD commit: 3cb12d27 Merge tag 'net-5.10-rc1' of git://git.kernel.org/.. > > In [1] you mentioned that dma_mask should not be set for dma_virt_ops. > So patch [2] removed it. > > But check to validate the dma mask for all dma_ops was added in [3]. > > What is the right way? Did I misunderstood your comment about dma_mask in [1]? No, I did not say we don't need the mask. I said copying over the various dma-related fields from the parent is bogus. I think rxe (and ther other drivers/infiniband/sw drivers) need a simple dma_coerce_mask_and_coherent and nothing else.