Re: [PATCH] Avoid that SCSI device removal through sysfs triggers a deadlock

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

 



On 10/27/2016 02:46 AM, Johannes Thumshirn wrote:
On Wed, Oct 26, 2016 at 11:44:51AM -0700, Bart Van Assche wrote:
+static void scsi_remove_device_async(struct scsi_device *sdev)
+{
+	if (scsi_device_get(sdev) < 0)

Nit: the < 0 could be dropped, scsi_device_get returns either -ENXIO or
0. But no reason to respin.

Anyways,
Reviewed-by: Johannes Thumshirn <jthumshirn@xxxxxxx>

Hello Johannes,

Thanks for the review. But I'd like to clarify that I added the "< 0" on purpose. Some *_get*() functions in the Linux kernel return 0 upon failure (e.g. kref_get_unless_zero()) and others a negative value (e.g. scsi_device_get()). The "< 0" part avoids that someone who reads this code has to look up what return value convention scsi_device_get() uses.

Bart.

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux