Received: by 10.213.65.68 with SMTP id h4csp2457763imn; Mon, 2 Apr 2018 07:57:02 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/p3zT953GAVdYaa30tip4rESntNWpe6gqZ1NA3iQkEfAZfCorObxuyOtIjfq/1mL+fgJij X-Received: by 10.98.217.88 with SMTP id s85mr7675599pfg.20.1522681022004; Mon, 02 Apr 2018 07:57:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522681021; cv=none; d=google.com; s=arc-20160816; b=PkIR+EBmZ4/rTWi/rJIYCEAEkK0DFKeIgO8sJ4eGseB5rBJrfDQW5QshXA1ww9Wy2L ogYRxtOFvcllhpRNYDEwz0J1Movnjq5EW6WVYhB6PaYQYyogb5s4651PcJbC5OKCB61c MWKkL+pFWl3xSu+YxIWEKjBNLlcx4gWtOwhcUyqYCK+OvJc9bs4ORY5Rl/dx8zeiQpnB GMXdgSmABQFysytVjTy51TJn+k/2iEE/+ck08JzfKCxloexfcbf4Lp9P+W3WX22YYnJf tRggyTQDKFHobPY+WtWWSfdVX4irvT6GS2WEQDIIXn+cxt3i5yiF3zl4K/IN261QKRsM shhA== 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:arc-authentication-results; bh=AFLpjNEt4h9feOgQzrgPcAR8AIOwcBCDxMRDsa7Wbac=; b=MU55IbxzNGciAdcNW7Th8lLbA6v6NZh/fvVwQDk7xb0maJp/5voAZvj3D01fbzMOmf db2WMJSNmQNeyRmg0zYByZGxvTDxTK5bcjeW8QSl487pXUsvr3WneS3/qDSHOwg8JDuX BbEilfYn1l6NTkiLHfx2O3uhIEvvduYElqth0492avSMhjkMb6CAew/+NzFgU08heJpD 7C0/yhTcC3S+Y23lkmLtn/BanaRYccVEVVI8KXPiJraxhUY4seFbHyOEyf8q+F3j3DyM pSitpd5Lr6AkpEiSRl42icK3SeyVntxm4vrZ1UZaFbkDlkunfzkkitTmMdvtNEthI8nU VfuQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v72si298564pgb.333.2018.04.02.07.56.47; Mon, 02 Apr 2018 07:57:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751735AbeDBOzi (ORCPT + 99 others); Mon, 2 Apr 2018 10:55:38 -0400 Received: from mga18.intel.com ([134.134.136.126]:47287 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751131AbeDBOzh (ORCPT ); Mon, 2 Apr 2018 10:55:37 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Apr 2018 07:55:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,395,1517904000"; d="scan'208";a="30418714" Received: from unknown (HELO localhost.localdomain) ([10.232.112.44]) by orsmga008.jf.intel.com with ESMTP; 02 Apr 2018 07:55:36 -0700 Date: Mon, 2 Apr 2018 08:58:13 -0600 From: Keith Busch To: "Rodrigo R. Galvao" Cc: hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] nvmet: fix nvmet_execute_write_zeroes function Message-ID: <20180402145813.GE28945@localhost.localdomain> References: <1522680581-10220-1-git-send-email-rosattig@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1522680581-10220-1-git-send-email-rosattig@linux.vnet.ibm.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 02, 2018 at 11:49:41AM -0300, Rodrigo R. Galvao wrote: > When trying to issue write_zeroes command against TARGET with a 4K block > size, it ends up hitting the following condition at __blkdev_issue_zeroout: > > if ((sector | nr_sects) & bs_mask) > return -EINVAL; > > Causing the command to always fail. > Considering we need to add 1 to get the correct block count, that addition > needs to be performed in the native format, so we moved the +1 to within > le16_to_cpu prior to converting to 512b. > > Signed-off-by: Rodrigo R. Galvao > --- > drivers/nvme/target/io-cmd.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/nvme/target/io-cmd.c b/drivers/nvme/target/io-cmd.c > index 28bbdff..5292bc3 100644 > --- a/drivers/nvme/target/io-cmd.c > +++ b/drivers/nvme/target/io-cmd.c > @@ -173,8 +173,8 @@ static void nvmet_execute_write_zeroes(struct nvmet_req *req) > > sector = le64_to_cpu(write_zeroes->slba) << > (req->ns->blksize_shift - 9); > - nr_sector = (((sector_t)le16_to_cpu(write_zeroes->length)) << > - (req->ns->blksize_shift - 9)) + 1; > + nr_sector = (((sector_t)le16_to_cpu(write_zeroes->length + 1)) << > + (req->ns->blksize_shift - 9)); I'm terribly sorry, but the +1 actually needs to be outside the le16_to_cpu. The above will work on little-endian machines, but not big.