Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1789841pxb; Fri, 5 Feb 2021 01:13:03 -0800 (PST) X-Google-Smtp-Source: ABdhPJx2qtJlsgbkW6is/Fnnspv6ibFxKyWm0vHaJ6WPKF6Ek0oPPSL+B/uy9DXZoi53GcIM7dxG X-Received: by 2002:a17:907:20c4:: with SMTP id qq4mr2336842ejb.495.1612516383312; Fri, 05 Feb 2021 01:13:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612516383; cv=none; d=google.com; s=arc-20160816; b=LAEwfGFLtgB8/25fwfLcmi/X2YPqCRgGKjPfNwSb3vz6ujmy/nd4Zwe5ENMGj0NEOo kBzvCg7VnWhyBp60jfXfiv2jJBiBw1JT+sGYYFkcp0dYNXQgBKScBx858U62vVmh/kfD o/mUztf6RxxFz3gsat3N+TQ/m5bHsC7FsxBrUDcvOg6TeaEgXTKkAH6s+igaxBI6H9zw TvbqRdqw1G0djsrzckg2Pw2UUkJ6rWJK/vjSmWnJL9Mob1ZkzC0pEcspObajy7EkqHKp brlxnVjgKYNUGQEFdoZhHfywcVBtQT6qP8D9UX6KE02PmoTONchFdDJ2OHe5lZW8hsXg EEVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=j0g3MEuv+YFAEugJs8NOIBW0mTSV3dOSXdpJKKD5GY8=; b=AtNlwu4OVFSHU9WFqLWakoJWag6jQsUKxV2IrtqUZAUioj4ydzPA2nKvi4CwICmnHV MUMFCPhlxb36urcgBo2SSzipOXWgmqfjTEBWMGcLG1ABJAaQSfOBtQVShalIMTYjoA1O asEr2/BapA2P7DSFR76OKHdYo2kgvVqd1UFb1eG5vqI2Vns4mOfXAUhdXrtx9h8D0Phb UCITySMLYz4Irv+8Am6cOh4sjPIzgZajxDZjdvyp9CVOASGlDQeu7DvqsaCH/PP+spkV rF//9My1VnTlswmlhBcvv3gqUtW7J8Irc7+bVXh1P9C3vFyrHr0QAXeAlMS3ZTHlaZ9L 1qhQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@foss.st.com header.s=selector1 header.b=kH2VenhB; 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=foss.st.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k23si4659166ejq.693.2021.02.05.01.12.38; Fri, 05 Feb 2021 01:13:03 -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=@foss.st.com header.s=selector1 header.b=kH2VenhB; 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=foss.st.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229511AbhBEJIu (ORCPT + 99 others); Fri, 5 Feb 2021 04:08:50 -0500 Received: from mx07-00178001.pphosted.com ([185.132.182.106]:46409 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229514AbhBEJGZ (ORCPT ); Fri, 5 Feb 2021 04:06:25 -0500 Received: from pps.filterd (m0046668.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 1159222J010299; Fri, 5 Feb 2021 10:05:24 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h=subject : to : cc : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=selector1; bh=j0g3MEuv+YFAEugJs8NOIBW0mTSV3dOSXdpJKKD5GY8=; b=kH2VenhB+dEQpaWqkHi30IdNh4eIZP32ZjOPXQ7nUuaFlw4/EHPB/EwJrGIHxMOdKVNE QyRsr4skH8GpI3sBdjuAW0BCDxfK8cmOjbgVmDyd+tjQgSUjQ8oUuK2Yk5vNa+3Ek4hw dJNoHx4/+6Gmk6blzPPhsMGvnhMf1YuZ4ZQEo/qbr0PJWpWtfg9q9IKstMNrb7K4Yxk/ 4thO7CmPugSWp7td+JH1EzrR14BO9T7owC+yDmVbvGQOFiPPtp3mlruMep8lN+2Wq1li 2Rmj/RL5PxR7IGCfXEKsc+J061C74EhqQ6h7q/zjGcn1M8dLqVd7yonWe1c2RZ81+mKx VA== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com with ESMTP id 36d0fsderx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 05 Feb 2021 10:05:24 +0100 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id C2F631001EB; Fri, 5 Feb 2021 10:05:22 +0100 (CET) Received: from Webmail-eu.st.com (sfhdag2node3.st.com [10.75.127.6]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id A6C7E221F7A; Fri, 5 Feb 2021 10:05:22 +0100 (CET) Received: from lmecxl0504.lme.st.com (10.75.127.50) by SFHDAG2NODE3.st.com (10.75.127.6) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 5 Feb 2021 10:05:21 +0100 Subject: Re: [PATCH 2/2] mmc: mmc_test: use erase_arg for mmc_erase command To: Adrian Hunter , CC: , , , , , , , , , , , References: <20210204120547.15381-1-yann.gautier@foss.st.com> <20210204120547.15381-3-yann.gautier@foss.st.com> From: Yann GAUTIER Message-ID: Date: Fri, 5 Feb 2021 10:05:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.75.127.50] X-ClientProxiedBy: SFHDAG2NODE1.st.com (10.75.127.4) To SFHDAG2NODE3.st.com (10.75.127.6) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369,18.0.737 definitions=2021-02-05_06:2021-02-05,2021-02-05 signatures=0 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/5/21 7:33 AM, Adrian Hunter wrote: > On 4/02/21 2:05 pm, yann.gautier@foss.st.com wrote: >> From: Yann Gautier >> >> Since [1], the erase argument for mmc_erase() function is saved in >> erase_arg field of card structure. It is preferable to use it instead of >> hard-coded MMC_SECURE_ERASE_ARG, which from eMMC 4.51 spec is not >> recommended: >> "6.6.16 Secure Erase >> NOTE Secure Erase is included for backwards compatibility. New system >> level implementations (based on v4.51 devices and beyond) should use >> Erase combined with Sanitize instead of secure erase." >> >> [1] commit 01904ff77676 ("mmc: core: Calculate the discard arg only once") >> > > Did you experience an issue because of this? You could add that to the > commit message. Hi Adrian, Thanks for the review! Yes, I've seen an issue on STM32MP157C-EV1 board. After a write test (e.g. test 36), the tests 37 or 38, using mmc_erase fail. With the erase argument used by default in the framework (MMC_DISCARD_ARG), I can no more see this. I can send a new version of the series with comment update here, and a fixup on the first patch. Regards, Yann > > There does not seem to be a need for secure erase, so: > > Acked-by: Adrian Hunter > > >> Signed-off-by: Yann Gautier >> --- >> drivers/mmc/core/mmc_test.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/drivers/mmc/core/mmc_test.c b/drivers/mmc/core/mmc_test.c >> index 39a478874ca3..63524551a13a 100644 >> --- a/drivers/mmc/core/mmc_test.c >> +++ b/drivers/mmc/core/mmc_test.c >> @@ -2110,7 +2110,7 @@ static int mmc_test_rw_multiple(struct mmc_test_card *test, >> if (mmc_can_erase(test->card) && >> tdata->prepare & MMC_TEST_PREP_ERASE) { >> ret = mmc_erase(test->card, dev_addr, >> - size / 512, MMC_SECURE_ERASE_ARG); >> + size / 512, test->card->erase_arg); >> if (ret) >> ret = mmc_erase(test->card, dev_addr, >> size / 512, MMC_ERASE_ARG); >> >