Re: EH method APIs

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

 



On Fri, Apr 04, 2014 at 09:36:54AM +0200, Hannes Reinecke wrote:
> Have to look into this. Problem is that some eh_XXX callback
> implementations actually are using the command to send the TMF;
> will need to look into them how and if they could be changed.

That's indeed a bit of a problem, guess we need to do an audit
on how the commands are used at the moment.

> Actually, alongside with that change I would update the arguments
> to the callback functions to align with the strategy level;
> eh_device_reset() would be getting struct scsi_device as argument,
> eh_target_reset() would get getting struct scsi_target as argument etc.
> 
> So the actual SCSI EH would not be tied to struct scsi_cmnd, and we
> would just be needing something to send TUR etc in the course of
> SCSI EH.

Right.  I think the commands should go through the normal BLOCK_PC code
path, we'd just need to make sure they get priority in the request
allocator.
--
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