On Wed, 6 Aug 2014, Christoph Hellwig wrote:

On Tue, Aug 05, 2014 at 05:02:46PM -0400, Chad Dupuis wrote:


On Tue, 5 Aug 2014, Venkatesh Srinivas wrote:

On Tue, Aug 5, 2014 at 12:45 PM, Chad Dupuis <chad.dup...@qlogic.com> wrote:
Set this to 1 for now as we've observed crashes when this is set to the default
value of 0.

What sorts of crashes have you seen with no_async_abort=0 (default)?
At which kernel versions?

We've seen a crash where we use a request that has already been used else
where when requeuing a SCSI command:

What kernel version is this one?  The last issues we saw in this area
were before we pulled fixes for these scenarios in:

d555a2abf3481f81303d835046a5ec2c4fb3ca8e
644373a4219add42123df69c8b7ce6a918475ccd
7daf480483e60898f30e0a2a84fecada7a7cfac0
c69e6f812bab0d5442b40e2f1bfbca48d40bc50b
8922a908908ff947f1f211e07e2e97f1169ad3cb
a33c070bced8b283e22e8dbae35177a033b810bf



This was on RHEL 7. Should we retry the test case with the latest mainline?
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to