On Tue, 2014-05-27 at 09:49 +0200, Bart Van Assche wrote: > On 05/26/14 17:27, James Bottomley wrote: > > On Mon, 2014-05-26 at 17:15 +0200, Bart Van Assche wrote: > >> Make it possible to test the REQ_ATOM_COMPLETE bit from outside the > >> block layer core. > > > > I don't see the value of patches 2,3 they're checking for an impossible > > condition ... why might it be possible? > > When reading the source code in scsi_error.c it's easy to overlook that > scmd_eh_abort_handler(), scsi_abort_command() and scsi_eh_scmd_add() are > all invoked for requests in which the REQ_ATOM_COMPLETE bit has been > set. I really don't like this entanglement of state of block and SCSI. "complete" in block terms isn't the same as in SCSI terms. The REQ_ATOM_COMPLETE flag is fully internal to block and indicates that we've taken over processing the command and any completions into block get ignored. This is for the possible race between timeout and inbound command completion. If you start coding SCSI assertions in terms of it, you're entangling layers that should be separate. The assertion in SCSI terms is that abort and ->done cannot race. James > Although it is possible to mention this as a comment above these > functions, such comments are not checked at runtime. It would require > additional work from the reader to verify whether or not such source > code comments are up to date. However, the condition inside a > WARN_ON_ONCE() statement is checked every time the code is executed. > Hence my preference for a WARN_ON_ONCE() statement instead of writing > down somewhere that these three functions operate on requests in which > the REQ_ATOM_COMPLETE bit has been set. -- 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
