Received: by 2002:a17:90a:9103:0:0:0:0 with SMTP id k3csp1188676pjo; Wed, 8 Jan 2020 13:29:34 -0800 (PST) X-Google-Smtp-Source: APXvYqxM4cLuruJKzTM7wgdMkySenf+okqeSLDrBee1a9oYX2QE7KTGl7SCGX7oh7NjIqqwhjdEe X-Received: by 2002:aca:b187:: with SMTP id a129mr526414oif.175.1578518973869; Wed, 08 Jan 2020 13:29:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578518973; cv=none; d=google.com; s=arc-20160816; b=sB08HNOLkWjnfe23TSHeCQHGMO/KScLYtyUZKXLxZ65rvzu+WPaJiEeXNXJDt/yDIM RSf92OnA8delm6tQLbQIUB7HeJqvNla828dUrQBP1VD2LOQGkdwlB6QIh7hvmMU6c5W0 RLk5qyvXo8+5yElgilFEvHomaf/U/O4/d9deee+4qzxAAaor0BekizQzQRNLvgwtDdlJ hjjPP7J38vquvpsvrDYVgcPHjqz6XhaGhl30fALUTsJF3Fm/duh/yTkkx//bFpXQje23 B3oYKZM+1X5s6936dTep/XHcTgHqjiwsXKeOn72JL+eOYbpoO6i0d3+vfZOcZWL0kUzt m72Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=PDndyIMuf+SGBEdpoWnLHWGwmjrUEAzXRO3SpvATPL0=; b=O2Dt7OGig2TGcUCPq+VRK0vZeAwMWOoI8qPuBoqOufWeenmrVC6rdlOGT9py1ya7DB Bx8pqn7GFhC0DrWO+AtI7+8Yr2QZTtUITTX4Due8y+ngOWO1qP5QEI5HULvc/VHCTPP+ Q3TKb1m1uw96MpzDbzI/A711oRKwxDgNitOIsjCQi/oK7Kmiu6wf2QonmYx+06S11n3e lJbqNrAAjpOrXIk9dWUvYS6TauBi7IKxBBUj0tOlszne09XO27yJWFXVqKJLb36+/hR3 p86R5hhEe+qjApQ6FBcPpJyatKqdbaeaF+32g8oQ2Ekw9NzDNsK51RTpr/VpyjbqBB3b ebSg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=bSxTH+eF; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u84si2361361oib.34.2020.01.08.13.29.20; Wed, 08 Jan 2020 13:29:33 -0800 (PST) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=bSxTH+eF; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726801AbgAHV2H (ORCPT + 99 others); Wed, 8 Jan 2020 16:28:07 -0500 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:44254 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725446AbgAHV2G (ORCPT ); Wed, 8 Jan 2020 16:28:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1578518885; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PDndyIMuf+SGBEdpoWnLHWGwmjrUEAzXRO3SpvATPL0=; b=bSxTH+eFoXprbPqFqggbi3I4IHLHPvJ/HThc1pxORpL+QTax/OEk8KABLdPDkll9d7oklU 1OB1G8siIiLjzrkTUu/joW4WGg8J37ZQW5xW/n96+qWAuV/D9x2L70sz/zSQouwBI9TNnP bomAG5cGzjobRRSWMslf5R306g+CamM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-382-dStVFU0HPOeWpx54NiZpYw-1; Wed, 08 Jan 2020 16:28:02 -0500 X-MC-Unique: dStVFU0HPOeWpx54NiZpYw-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 32852800D48; Wed, 8 Jan 2020 21:28:00 +0000 (UTC) Received: from emilne (unknown [10.18.25.205]) by smtp.corp.redhat.com (Postfix) with ESMTP id 7F3607C3AD; Wed, 8 Jan 2020 21:27:56 +0000 (UTC) Message-ID: Subject: Re: [resend v1 5/5] drivers/scsi/sd.c: Convert to use disk_set_capacity From: "Ewan D. Milne" To: "Martin K. Petersen" Cc: James Bottomley , axboe@kernel.dk, Chaitanya.Kulkarni@wdc.com, mst@redhat.com, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, linux-block@vger.kernel.org, ssomesh@amazon.com, Balbir Singh , hch@lst.de Date: Wed, 08 Jan 2020 16:27:55 -0500 In-Reply-To: References: <20200102075315.22652-1-sblbir@amazon.com> <20200102075315.22652-6-sblbir@amazon.com> <1578369479.3251.31.camel@linux.ibm.com> <1eb9d796f81fffbb0bfe90bff8460bcda34cb04d.camel@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2020-01-07 at 21:59 -0500, Martin K. Petersen wrote: > Ewan, > > > Yes, there are some storage arrays that refuse a READ CAPACITY > > command in certain ALUA states so you can't get the new capacity > > anyway. > > Yep. And some devices will temporarily return a capacity of > 0xFFFFFFFF... If we were to trigger a filesystem resize, the results > would be disastrous. > > > It might be nice to improve this, though, there are some cases now > > where we set the capacity to zero when we revalidate and can't get the > > value. > > If you have a test case, let's fix it. > This happens with NVMe fabric devices, I thought. I'll check.