Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932324AbZIRTeG (ORCPT ); Fri, 18 Sep 2009 15:34:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758037AbZIRTd7 (ORCPT ); Fri, 18 Sep 2009 15:33:59 -0400 Received: from out02.mta.xmission.com ([166.70.13.232]:47616 "EHLO out02.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757789AbZIRTd6 (ORCPT ); Fri, 18 Sep 2009 15:33:58 -0400 To: Kay Sievers Cc: Arjan van de Ven , Linus Torvalds , linux-kernel@vger.kernel.org, Greg Kroah-Hartmann References: <20090918160944.58e5c1f5@infradead.org> <20090918162503.6735cc1b@infradead.org> <20090918164331.24403a5d@infradead.org> <20090918171328.7a102223@infradead.org> From: ebiederm@xmission.com (Eric W. Biederman) Date: Fri, 18 Sep 2009 12:33:54 -0700 In-Reply-To: (Kay Sievers's message of "Fri\, 18 Sep 2009 17\:32\:18 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-XM-SPF: eid=;;;mid=;;;hst=in01.mta.xmission.com;;;ip=76.21.114.89;;;frm=ebiederm@xmission.com;;;spf=neutral X-SA-Exim-Connect-IP: 76.21.114.89 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-DCC: XMission; sa04 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Kay Sievers X-Spam-Relay-Country: X-Spam-Report: * -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.0 T_TM2_M_HEADER_IN_MSG BODY: T_TM2_M_HEADER_IN_MSG * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa04 1397; Body=1 Fuz1=1 Fuz2=1] * 0.1 XMSolicitRefs_0 Weightloss drug * 0.0 XM_SPF_Neutral SPF-Neutral * 0.4 UNTRUSTED_Relay Comes from a non-trusted relay Subject: Re: [PATCH] Remove broken by design and by implementation devtmpfs maintenance disaster X-SA-Exim-Version: 4.2.1 (built Thu, 25 Oct 2007 00:26:12 +0000) X-SA-Exim-Scanned: Yes (on in01.mta.xmission.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 547 Lines: 18 As for losetup. Arguably the right way to handle that one is the old fashioned way: mknod /dev/loop0 losetup /dev/loop0 In that case the kernel calls modprobe for us. I don't see why we should have a race in the first place. Even calling modprobe explicitly seems like a hack in this case. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/