Re: [PATCH v3 0/2] Fix scsi device's iodone_cnt mismatch with iorequest_cnt

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

To: Wenchao Hao <haowenchao@xxxxxxxxxx>
Subject: Re: [PATCH v3 0/2] Fix scsi device's iodone_cnt mismatch with iorequest_cnt
From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
Date: Wed, 23 Nov 2022 22:42:15 -0500
Cc: Lee Duncan <lduncan@xxxxxxxx>, Chris Leech <cleech@xxxxxxxxxx>, "Mike Christie" <michael.christie@xxxxxxxxxx>, "James E . J . Bottomley" <jejb@xxxxxxxxxxxxx>, "Martin K . Petersen" <martin.petersen@xxxxxxxxxx>, <open-iscsi@xxxxxxxxxxxxxxxx>, <linux-scsi@xxxxxxxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <liuzhiqiang26@xxxxxxxxxx>, <linfeilong@xxxxxxxxxx>
In-reply-to: <20221123122137.150776-1-haowenchao@huawei.com> (Wenchao Hao's message of "Wed, 23 Nov 2022 20:21:35 +0800")
Organization: Oracle Corporation

Wenchao,

> Following scenario would make scsi_device's iodone_cnt mismatch with
> iorequest_cnt even if there is no request on this device any more.

Applied to 6.2/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

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

References:
- [PATCH v3 0/2] Fix scsi device's iodone_cnt mismatch with iorequest_cnt
  - From: Wenchao Hao

Prev by Date: Re: [PATCH] scsi:iscsi: rename iscsi_set_param to iscsi_if_set_param
Next by Date: Why is MEGASAS_SAS_QD set to 256?
Previous by thread: [PATCH v3 1/2] scsi: increase scsi device's iodone_cnt in scsi_timeout()
Next by thread: Re: [PATCH v3 0/2] Fix scsi device's iodone_cnt mismatch with iorequest_cnt
Index(es):
- Date
- Thread

[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