Received: by 10.213.65.68 with SMTP id h4csp2453708imn; Mon, 2 Apr 2018 07:52:27 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/OncEKSYauprMbO7400INWLAv0p6Xc7jFt8Nq/ZFZeloHOkiitzGgcehFCRm68Vn7q7NeP X-Received: by 10.98.138.205 with SMTP id o74mr7673243pfk.114.1522680747642; Mon, 02 Apr 2018 07:52:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522680747; cv=none; d=google.com; s=arc-20160816; b=vqcd5Oy9rX9jUOmCea3ovKFT8DEvzzp9JL0zsyNQLuV5o/Ay4L3dTO+hlAD2FsrUWC r2/oCALERK0NPfrem6I0z1ZEd9tWLI3x+swBDtK9dGBoKlPbpjY99L3SqQrtwVxyJn8l LTHEoSY3/6rCqKoFVJiu9MSn8H22DMzZSftap+21ZJdBcg2qaWQg87IIew74039jxLrJ g7o9vcrVKEbeMicXtRQqHc2HkHukVTqU7+F23cSfzgqA1vd9MZI3n1ksWfTFRZ+G8Oi/ XowdOirZzI+6zSuhvp/Ve2isXH7r094ri2+Mr9x2jYRmJ7yKhLknxSABKtXU6Vek20rg YGZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :from:references:cc:to:subject:arc-authentication-results; bh=8xZH2zNoGJaOFc9ca3w4dxoXbYbxz2dW5LVC8RPpE1A=; b=cp+aFkozZRoT3cVrC0QuXSI6wi8fEGCfoAfcKZY++wZsIgs16CCvzP2FLWUrzFKapp IpoqkPex31GduXiY5Wd+kImWyCVgfJSuA6epbesEukG7cAscJAcYAeuNBx98xwPkfifc SWcu0TGfcQn6A2xpM4AobndepTCc/up+9PCDdF5hNm0L3Ydi4u8uyQdE78RNQNuBJXaH sdx8IEqPxcFinzgiLj/uNlYFHXzQqtf9n66rhQPLtbYwPDlXn/zqio4lFPl7C9c1V4q7 qXR6wUUHnOE01ufir04KlDRpmY4R2tETESbCttIytynZtiwjFii8BZAguSRIUKgKCxNM JlmA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v12-v6si458874plk.615.2018.04.02.07.52.13; Mon, 02 Apr 2018 07:52:27 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752093AbeDBOuy (ORCPT + 99 others); Mon, 2 Apr 2018 10:50:54 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:46100 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751255AbeDBOux (ORCPT ); Mon, 2 Apr 2018 10:50:53 -0400 Received: from pps.filterd (m0098410.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w32EoaY8142824 for ; Mon, 2 Apr 2018 10:50:53 -0400 Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by mx0a-001b2d01.pphosted.com with ESMTP id 2h3napbs5t-1 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NOT) for ; Mon, 02 Apr 2018 10:50:53 -0400 Received: from localhost by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 2 Apr 2018 08:50:52 -0600 Received: from b03cxnp07029.gho.boulder.ibm.com (9.17.130.16) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 2 Apr 2018 08:50:48 -0600 Received: from b03ledav005.gho.boulder.ibm.com (b03ledav005.gho.boulder.ibm.com [9.17.130.236]) by b03cxnp07029.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w32EobFl4522338; Mon, 2 Apr 2018 07:50:48 -0700 Received: from b03ledav005.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7827ABE05D; Mon, 2 Apr 2018 08:50:48 -0600 (MDT) Received: from rosattig.br.ibm.com (unknown [9.18.239.102]) by b03ledav005.gho.boulder.ibm.com (Postfix) with ESMTP id EE99EBE03B; Mon, 2 Apr 2018 08:50:46 -0600 (MDT) Subject: Re: [PATCH] nvmet: fix nvmet_execute_write_zeroes function To: Keith Busch Cc: Sagi Grimberg , Chaitanya Kulkarni , linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, chaitany kulkarni , hch@lst.de References: <1522444730-2060-1-git-send-email-rosattig@linux.vnet.ibm.com> <20180330212439.GA28945@localhost.localdomain> <93622938-f532-b8ac-2bca-fe40ed759e71@linux.vnet.ibm.com> <8a3d1471-571d-3352-1414-bf2051e2ebb9@linux.vnet.ibm.com> <20180402142141.GC28945@localhost.localdomain> From: Rodrigo Rosatti Galvao Date: Mon, 2 Apr 2018 11:50:45 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180402142141.GC28945@localhost.localdomain> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-TM-AS-GCONF: 00 x-cbid: 18040214-0008-0000-0000-0000098AC831 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00008789; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000255; SDB=6.01012065; UDB=6.00515771; IPR=6.00791338; MB=3.00020376; MTD=3.00000008; XFM=3.00000015; UTC=2018-04-02 14:50:51 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18040214-0009-0000-0000-000046A3959C Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-04-02_07:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1804020166 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thanks Keith. The patch you proposed worked fine!! I just sent a V2 with that change! On 04/02/2018 11:21 AM, Keith Busch wrote: > On Mon, Apr 02, 2018 at 10:47:10AM -0300, Rodrigo Rosatti Galvao wrote: >> One thing that I just forgot to explain previously, but I think its >> relevant: >> >> 1. The command is failing with 4k logical block size, but works with 512B >> >> 2. With the patch, the command is working for both 512B and 4K. > While you're not getting errors with your patch, you're not zeroing out > the requested blocks, so that's a data corruption. > > The issue is the +1 is in the wrong place. It needs to be added to the > native format prior to converting it to a 512b sector count. Do you want > to resend with that change? > > _______________________________________________ > Linux-nvme mailing list > Linux-nvme@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-nvme > -- Rodrigo R. Galvão Intern - Linux Technology Center - IBM