Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp810295pxb; Thu, 28 Jan 2021 00:10:16 -0800 (PST) X-Google-Smtp-Source: ABdhPJz3YuciUYmuIOEC2vqCsMu2lEedsLvuH9AxK1dR8GTIuKC9AJYpjc9GdiykPYmaDVdoF1EP X-Received: by 2002:a17:906:6407:: with SMTP id d7mr8493224ejm.133.1611821416219; Thu, 28 Jan 2021 00:10:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611821416; cv=none; d=google.com; s=arc-20160816; b=XRIku7+6584pnaDUESTPl94Z7Vb2QOHXKdEbKUYNJRn5U+O9+jLqqX5R+TS79TINJt ncCyTE0tQ6QRLZlowDwlHsCl8c/FBZ8bnSougOwig4OyKQO6A/GbcAY4Wupi1gBq1jtw S9ygKDidosufOauPD+i6Ez+0qg8FGawhAieuRa3zpzgrdObvbCmt7uvdwP21QueIeprB SJkNl5Mnwc/zZKLlS3GT4hcmvLrYZ+OcyzsLcLHdaetXbvWyIpzVgrLFzqKObIyTTIDB cr8+uk9/JoJErBnKgWSlmPXDKRCDi8wur+dOTVIZbRerCcPYh0MiS9PS8LI8+Xa58pv0 ZkzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=9mK/OlZMxGlbMAHphPES28w+zvOVN1hxVkpikcJNyI8=; b=00jkErdr60FLeGSrzGjT5TNxqaL8SjqiPd1RvvtVs/rwaWfjcsXeuYOBepY+m91gAO +eGfhf6bvhIIYn35mxSOhb75lBDqiI+aZD6fypmeKSAefMPztDYb4H6/MSEOQH/L5pnB JWr4K4Y9hqYeEtIwnwwX1Nm/slZIwit98kqyWwMtWu6OS6fGNYdPQGq9UGDNc56Q4xxm lQtGvwzi3RmusF9flMyViYtVMPZ/Bw2yVdWeb2o3Cx5lCcaFkvIpPP00N3BhfdOj73yg KnqlpyGPmxVpRoRKwMigXo1B9D7lOOqOdAG4S4XQ1hNQMV7fs3qq+JP8FDvYjN6rAbJp Xb/w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=PJNlFazu; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t12si2599781edc.228.2021.01.28.00.09.52; Thu, 28 Jan 2021 00:10:16 -0800 (PST) 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; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=PJNlFazu; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232249AbhA1IGK (ORCPT + 99 others); Thu, 28 Jan 2021 03:06:10 -0500 Received: from mail.kernel.org ([198.145.29.99]:39522 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232308AbhA1IFe (ORCPT ); Thu, 28 Jan 2021 03:05:34 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 16D4B64DDA; Thu, 28 Jan 2021 08:04:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1611821094; bh=GuLi/8pmF+rCgjPXwttqZpfpUDWjxcO0+aBtX7a6cpk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=PJNlFazuzogyHS95uUijQnggfofbJSHp4E1kJjQrb9wi7AOPHtoRGgcFljLsNPOsI dAiKEea5u8NcfJs6yeXLXdg4+We5/Nt6h5G8s9pjXEpsTUNn2Mz9zTaovvLzmjt7EE JfRf+akhzadrBzz//k88tU5HlhLlEJyPUsxYYbZI= Date: Thu, 28 Jan 2021 09:04:50 +0100 From: Greg KH To: Jianxiong Gao Cc: erdemaktas@google.com, marcorr@google.com, hch@lst.de, m.szyprowski@samsung.com, robin.murphy@arm.com, saravanak@google.com, heikki.krogerus@linux.intel.com, rafael.j.wysocki@intel.com, andriy.shevchenko@linux.intel.com, dan.j.williams@intel.com, bgolaszewski@baylibre.com, jroedel@suse.de, iommu@lists.linux-foundation.org, konrad.wilk@oracle.com, kbusch@kernel.org, axboe@fb.com, sagi@grimberg.me, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] Adding offset keeping option when mapping data via SWIOTLB.* Message-ID: References: <20210128003829.1892018-1-jxgao@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210128003829.1892018-1-jxgao@google.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 27, 2021 at 04:38:26PM -0800, Jianxiong Gao wrote: > NVMe driver and other applications may depend on the data offset > to operate correctly. Currently when unaligned data is mapped via > SWIOTLB, the data is mapped as slab aligned with the SWIOTLB. This > patch adds an option to make sure the mapped data preserves its > offset of the orginal addrss. > > Without the patch when creating xfs formatted disk on NVMe backends, > with swiotlb=force in kernel boot option, creates the following error: > meta-data=/dev/nvme2n1 isize=512 agcount=4, agsize=131072 blks > = sectsz=512 attr=2, projid32bit=1 > = crc=1 finobt=1, sparse=0, rmapbt=0, refl > ink=0 > data = bsize=4096 blocks=524288, imaxpct=25 > = sunit=0 swidth=0 blks > naming =version 2 bsize=4096 ascii-ci=0 ftype=1 > log =internal log bsize=4096 blocks=2560, version=2 > = sectsz=512 sunit=0 blks, lazy-count=1 > realtime =none extsz=4096 blocks=0, rtextents=0 > mkfs.xfs: pwrite failed: Input/output error > > Jianxiong Gao (3): > Adding page_offset_mask to device_dma_parameters > Add swiotlb offset preserving mapping when > dma_dma_parameters->page_offset_mask is non zero. > Adding device_dma_parameters->offset_preserve_mask to NVMe driver. Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - You did not write a descriptive Subject: for the patch, allowing Greg, and everyone else, to know what this patch is all about. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what a proper Subject: line should look like. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot