Re: [PATCH v4 13/37] target: Stop execution if CMD_T_STOP has been set

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

 



On Wed, 2017-02-08 at 14:24 -0800, Bart Van Assche wrote:
> Stop execution if CMD_T_STOP has been set for a command just after
> the command has been added to the device command list and before
> .write_pending() is called. The following sequence can trigger this:
> - transport_handle_cdb_direct() gets called. This function namely
>   sets CMD_T_ACTIVE before it calls transport_generic_new_cmd().
> - __transport_wait_for_tasks() is called concurrently. This function
>   sets CMD_T_STOP for all active commands that have not been aborted.
> 
> Signed-off-by: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
> Reviewed-by: Hannes Reinecke <hare@xxxxxxxx>
> Cc: Christoph Hellwig <hch@xxxxxx>
> Cc: Andy Grover <agrover@xxxxxxxxxx>
> Cc: David Disseldorp <ddiss@xxxxxxx>
> ---

Applied.

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



[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux