Re: [PATCH v2 16/36] target: Stop execution if CMD_T_STOP has been set

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

 



On Mon, 2017-02-06 at 01:14 -0800, Christoph Hellwig wrote:
> On Wed, Feb 01, 2017 at 04:58:33PM -0800, Bart Van Assche wrote:
> > Stop execution in the unlikely scenario that 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.
> 
> How could this happen?

Hello Christoph,

Since this call of transport_cmd_check_stop() occurs before command
execution starts and hence before CMD_T_ACTIVE is set
__transport_wait_for_tasks() cannot yet have set CMD_T_STOP. If you
want I can drop this patch.

Bart.--
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