[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1578369479.3251.31.camel@linux.ibm.com>
Date: Mon, 06 Jan 2020 19:57:59 -0800
From: James Bottomley <jejb@...ux.ibm.com>
To: "Martin K. Petersen" <martin.petersen@...cle.com>,
Balbir Singh <sblbir@...zon.com>
Cc: linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
linux-nvme@...ts.infradead.org, axboe@...nel.dk,
ssomesh@...zon.com, hch@....de, mst@...hat.com,
Chaitanya.Kulkarni@....com
Subject: Re: [resend v1 5/5] drivers/scsi/sd.c: Convert to use
disk_set_capacity
On Mon, 2020-01-06 at 22:48 -0500, Martin K. Petersen wrote:
> Balbir,
>
> > diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> > index 5afb0046b12a..1a3be30b6b78 100644
> > --- a/drivers/scsi/sd.c
> > +++ b/drivers/scsi/sd.c
> > @@ -3184,7 +3184,7 @@ static int sd_revalidate_disk(struct gendisk
> > *disk)
> >
> > sdkp->first_scan = 0;
> >
> > - set_capacity(disk, logical_to_sectors(sdp, sdkp-
> > >capacity));
> > + disk_set_capacity(disk, logical_to_sectors(sdp, sdkp-
> > >capacity));
> > sd_config_write_same(sdkp);
> > kfree(buffer);
>
> We already emit an SDEV_EVT_CAPACITY_CHANGE_REPORTED event if device
> capacity changes. However, this event does not automatically cause
> revalidation.
Which I seem to remember was a deliberate choice: some change
capacities occur because the path goes passive and default values get
installed.
James
Powered by blists - more mailing lists