On Wed, Aug 06, 2014 at 04:01:12PM -0400, Chad Dupuis wrote:
> This was on RHEL 7. Should we retry the test case with the latest
> mainline?
Yes. Please always test your patches against latest mainline. If that is
for some reason not possible please at least very prominently mention that
the i
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 wrote:
Set this to 1 for now as we've observed crashes when this is set to the default
val
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 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 cra
On Tue, 5 Aug 2014, Venkatesh Srinivas wrote:
On Tue, Aug 5, 2014 at 12:45 PM, Chad Dupuis 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'
On Tue, Aug 5, 2014 at 12:45 PM, Chad Dupuis 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?
Thanks,
-- vs;
--
To unsubscribe from this list: s
5 matches
Mail list logo
