Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp221699pxk; Thu, 1 Oct 2020 00:15:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxdeTM1xmc6gI/IImFZUooZ9kwte0+J7G/9AMO7XJlsOjaa4WawP1xEByBxqSbr+FhNUm2V X-Received: by 2002:a50:fe0f:: with SMTP id f15mr6601367edt.235.1601536514562; Thu, 01 Oct 2020 00:15:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601536514; cv=none; d=google.com; s=arc-20160816; b=XnsOqtP93715mIVgq6vEBRXJ+nv0U3CIUSyVNnjkoHu2/y6bcE6TqI8D4EMz1Yfyka A+R29ZyDdVj2w2ASvy/76IL8etIPxDiKMTjzRrRWjNc/AtSVPTLM0N6UhB3skIP/iQ/t 2x0hCU4wCwWeAxK3jI1XFJu4SkMWNeO/yMURhxnTj3o9zoWTJCQF/LpawBTVZb6vEoP4 RlVn/oYmVbXxddrdlGbTk48fx7o23qpT4j5z8LTiio8qMsVGxzFJl5L3B/+2HLY45dVG NsCnZA1ARI02jfnQ+enQfJqW5W+R3AHfPRJ0D73YHkZZkg+4+O++g+6g1SYv7YG44OKM JEoA== 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:organization :from:references:cc:to:subject:ironport-sdr:ironport-sdr; bh=SglBulsWGPQ1n8piBk50WZ7ArZn05HbdEe2nRZFpFww=; b=vk2IDhBslQS684RqbbITeR/JDG+AWIZBjNUv2yuurNrphg8LZrdGMBSHFqx9085DMQ UzXRdmVDb+gP9lV8CYSDn9TxvCk5N2Cv3T0S8R7kqC5OumrlwIu3Xl9fVGUIXx8X0x0k b0SloB20Tz/n6GtSU4dEiQEkSAibdA2SiWM60wKyadq6m+BqAqYF8fvTytL5esD/6Sa8 XYCrF4+Z3OzVWIqhGxigVPmA0RPgMmofv/8maMFAOswRw3zS6wX+LQCwzNBEtd66XTsT /fbV0vXXq32IJkhQ5k9DRdcmTt9/Got/eHBZ+mhB+ypmjnoWCCduBm3f8fk9GnV8vkGI 36QQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id oq7si3144747ejb.650.2020.10.01.00.14.50; Thu, 01 Oct 2020 00:15:14 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730378AbgJAHNq (ORCPT + 99 others); Thu, 1 Oct 2020 03:13:46 -0400 Received: from mga18.intel.com ([134.134.136.126]:5771 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725878AbgJAHNq (ORCPT ); Thu, 1 Oct 2020 03:13:46 -0400 IronPort-SDR: kpsAF4EyWg/u1ggPocHHqz6mmsFh5pRewCSkt0+StU7NsR6qXHBT2MtqVo+7rQms0nmhLAIZ1c 3zEtJYvpG+tQ== X-IronPort-AV: E=McAfee;i="6000,8403,9760"; a="150433356" X-IronPort-AV: E=Sophos;i="5.77,323,1596524400"; d="scan'208";a="150433356" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Oct 2020 00:13:46 -0700 IronPort-SDR: 8aN7VyV3EimkkLyP7R0V+fDmzOOxgeKmllxlDZNhDJF/YWM4MGOOV+Q5121rRPudnd/ZI6B6hr SU76V3G1sKrQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,323,1596524400"; d="scan'208";a="502072813" Received: from ahunter-desktop.fi.intel.com (HELO [10.237.72.190]) ([10.237.72.190]) by orsmga005.jf.intel.com with ESMTP; 01 Oct 2020 00:13:43 -0700 Subject: Re: [PATCH v2] mmc: core: don't set limits.discard_granularity as 0 To: Coly Li , linux-mmc@vger.kernel.org Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Vicente Bergas , Ulf Hansson References: <20201001065914.24526-1-colyli@suse.de> From: Adrian Hunter Organization: Intel Finland Oy, Registered Address: PL 281, 00181 Helsinki, Business Identity Code: 0357606 - 4, Domiciled in Helsinki Message-ID: Date: Thu, 1 Oct 2020 10:13:10 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <20201001065914.24526-1-colyli@suse.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/10/20 9:59 am, Coly Li wrote: > In mmc_queue_setup_discard() the mmc driver queue's discard_granularity > might be set as 0 (when card->pref_erase > max_discard) while the mmc > device still declares to support discard operation. This is buggy and > triggered the following kernel warning message, > > WARNING: CPU: 0 PID: 135 at __blkdev_issue_discard+0x200/0x294 > CPU: 0 PID: 135 Comm: f2fs_discard-17 Not tainted 5.9.0-rc6 #1 > Hardware name: Google Kevin (DT) > pstate: 00000005 (nzcv daif -PAN -UAO BTYPE=--) > pc : __blkdev_issue_discard+0x200/0x294 > lr : __blkdev_issue_discard+0x54/0x294 > sp : ffff800011dd3b10 > x29: ffff800011dd3b10 x28: 0000000000000000 x27: ffff800011dd3cc4 x26: ffff800011dd3e18 x25: 000000000004e69b x24: 0000000000000c40 x23: ffff0000f1deaaf0 x22: ffff0000f2849200 x21: 00000000002734d8 x20: 0000000000000008 x19: 0000000000000000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000394 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000000 x10: 00000000000008b0 x9 : ffff800011dd3cb0 x8 : 000000000004e69b x7 : 0000000000000000 x6 : ffff0000f1926400 x5 : ffff0000f1940800 x4 : 0000000000000000 x3 : 0000000000000c40 x2 : 0000000000000008 x1 : 00000000002734d8 x0 : 0000000000000000 Call trace: > __blkdev_issue_discard+0x200/0x294 > __submit_discard_cmd+0x128/0x374 > __issue_discard_cmd_orderly+0x188/0x244 > __issue_discard_cmd+0x2e8/0x33c > issue_discard_thread+0xe8/0x2f0 > kthread+0x11c/0x120 > ret_from_fork+0x10/0x1c > ---[ end trace e4c8023d33dfe77a ]--- > > This patch fixes the issue by setting discard_granularity as SECTOR_SIZE > instead of 0 when (card->pref_erase > max_discard) is true. Now no more > complain from __blkdev_issue_discard() for the improper value of discard > granularity. > > This issue is explored after commit b35fd7422c2f ("block: check queue's explored -> exposed > limits.discard_granularity in __blkdev_issue_discard()"), therefore add > a "Fixes:" tag for the commit to make sure people won't miss this patch > after applying the change of __blkdev_issue_discard(). > > Fixes: b35fd7422c2f ("block: check queue's limits.discard_granularity in __blkdev_issue_discard()"). I thought you would keep the other fixes tag also > Reported-by: Vicente Bergas > Signed-off-by: Coly Li > Cc: Adrian Hunter > Cc: Ulf Hansson Otherwise: Acked-by: Adrian Hunter > --- > Changelog, > v2, change commit id of the Fixes tag. > v1, initial version. > > drivers/mmc/core/queue.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/mmc/core/queue.c b/drivers/mmc/core/queue.c > index 6c022ef0f84d..350d0cc4ee62 100644 > --- a/drivers/mmc/core/queue.c > +++ b/drivers/mmc/core/queue.c > @@ -190,7 +190,7 @@ static void mmc_queue_setup_discard(struct request_queue *q, > q->limits.discard_granularity = card->pref_erase << 9; > /* granularity must not be greater than max. discard */ > if (card->pref_erase > max_discard) > - q->limits.discard_granularity = 0; > + q->limits.discard_granularity = SECTOR_SIZE; > if (mmc_can_secure_erase_trim(card)) > blk_queue_flag_set(QUEUE_FLAG_SECERASE, q); > } >