linux-kernel - Re: I/O scheduler deadlocks on Xen virtual block devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <x49bp8gfeax.fsf@segfault.boston.devel.redhat.com>
Date:	Thu, 02 Sep 2010 09:47:02 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Doug Neal <dneallkml@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: I/O scheduler deadlocks on Xen virtual block devices

Doug Neal <dneallkml@...il.com> writes:

>>
>> Did you try these different I/O schedulers in the domU or on the dom0?
>> Does switching I/O schedulers in either place make the problem go away
>> when it happens?
>>
>
> In the domU, and the bug was present in all cases. The dom0 was using
> cfq. I'll run the tests again using each scheduler in the dom0 with
> domU set to noop and report back.

While I think this is an interesting test, you need only test one I/O
scheduler in the dom0.  Also, I think you misunderstood the second
question.  I'd like to know if switching I/O schedulers while the system
is in this bad state helps get I/O going again.

Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/