Re: [PATCH 05/10] nvme: don't blindly overwrite identifiers on disk revalidate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 28, 2017 at 09:17:44AM +0300, Sagi Grimberg wrote:
>> +	u8 eui64[8] = { 0 }, nguid[16] = { 0 };
>> +	uuid_t uuid = uuid_null;
>>   	int ret = 0;
>>     	if (test_bit(NVME_NS_DEAD, &ns->flags)) {
>> @@ -1252,7 +1254,15 @@ static int nvme_revalidate_disk(struct gendisk *disk)
>>   		goto out;
>>   	}
>>   -	nvme_report_ns_ids(ctrl, ns->ns_id, id, ns->eui, ns->nguid, 
>> &ns->uuid);
>> +	nvme_report_ns_ids(ctrl, ns->ns_id, id, eui64, nguid, &uuid);
>> +	if (!uuid_equal(&ns->uuid, &uuid) ||
>> +	    memcmp(&ns->nguid, &nguid, sizeof(ns->nguid)) ||
>> +	    memcmp(&ns->eui, &eui64, sizeof(ns->eui))) {
>
> Shouldn't uuid,nguid,eui64 record the previous values prior to calling
> nvme_report_ns_ids?

The previous values are still in the namespace structure, and we use
the on-stack variables for the current ones.



[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux