On Tue, Jan 15, 2013 at 6:52 PM, Tejun Heo <tj@xxxxxxxxxx> wrote:
>
> It makes me feel dirty but makes the problem go away and I can't think
> of anything better, so here is the implementation of "used async"
> workaround.
Ok, people, can we get a tested-by (or "Nope, doesn't work") from the
people who saw this?
That said, maybe we could just make the rule be that you can't pick a
default IO scheduler that is modular.
And I *would* like to see the warning we discussed. Maybe there are
other situations that can trigger this?
Because something like that
WARN_ON_ONCE(wait && i_am_async() && system_state == SYSTEM_RUNNING);
in kernel/kmod.c (__request_module()) still sounds like a good idea to
verify that this is the only thing that triggers it (of course, we'd
need to somehow avoid the warning for the known case with the known
workaround).
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
