From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757706Ab3APDAy (ORCPT ); Tue, 15 Jan 2013 22:00:54 -0500 Received: from mail-vc0-f175.google.com ([209.85.220.175]:47873 "EHLO mail-vc0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756664Ab3APDAw (ORCPT ); Tue, 15 Jan 2013 22:00:52 -0500 MIME-Version: 1.0 In-Reply-To: <20130116025251.GM2668@htj.dyndns.org> References: <20130115183204.GE2668@htj.dyndns.org> <20130115235043.GJ2668@htj.dyndns.org> <20130116025251.GM2668@htj.dyndns.org> From: Linus Torvalds Date: Tue, 15 Jan 2013 19:00:31 -0800 X-Google-Sender-Auth: aZg7FKMK9g10QeDMBT5atyoy5sU Message-ID: Subject: Re: [PATCH] module, async: async_synchronize_full() on module init iff async is used To: Tejun Heo Cc: Ming Lei , Alex Riesen , Alan Stern , Jens Axboe , USB list , Linux Kernel Mailing List , Arjan van de Ven , Rusty Russell Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 15, 2013 at 6:52 PM, Tejun Heo 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