i'm jumping in having the same problem as brendan. I bisected this myself. The offending commit is this one:
909657615d9b3ce709be4fd95b9a9e8c8c7c2be6 is the first bad commit
commit 909657615d9b3ce709be4fd95b9a9e8c8c7c2be6
Author: Christoph Hellwig <email address hidden>
Date: Thu Apr 6 15:36:32 2017 +0200
scsi: libsas: allow async aborts
We now first try to call ->eh_abort_handler from a work queue, but libsas
was always failing that for no good reason. Allow async aborts.
Reviewed-by: Johannes Thumshirn <email address hidden>
Reviewed-by: Hannes Reinecke <email address hidden>
Signed-off-by: Christoph Hellwig <email address hidden>
Signed-off-by: Martin K. Petersen <email address hidden>
:040000 040000 b15f1eb57bf74667aefb7a304fa09bf58386eaf2 64df540499763db44c7e1b6ec9a55ffa9b2ebedc M drivers
Hello,
i'm jumping in having the same problem as brendan. I bisected this myself. The offending commit is this one:
909657615d9b3ce 709be4fd95b9a9e 8c8c7c2be6 is the first bad commit 709be4fd95b9a9e 8c8c7c2be6
commit 909657615d9b3ce
Author: Christoph Hellwig <email address hidden>
Date: Thu Apr 6 15:36:32 2017 +0200
scsi: libsas: allow async aborts
We now first try to call ->eh_abort_handler from a work queue, but libsas
was always failing that for no good reason. Allow async aborts.
Reviewed-by: Johannes Thumshirn <email address hidden>
Reviewed-by: Hannes Reinecke <email address hidden>
Signed-off-by: Christoph Hellwig <email address hidden>
Signed-off-by: Martin K. Petersen <email address hidden>
:040000 040000 b15f1eb57bf7466 7aefb7a304fa09b f58386eaf2 64df540499763db 44c7e1b6ec9a55f fa9b2ebedc M drivers