From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from shards.monkeyblade.net ([198.137.202.13]:52724 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751209Ab1EPSND (ORCPT ); Mon, 16 May 2011 14:13:03 -0400 Date: Mon, 16 May 2011 14:11:58 -0400 (EDT) Message-Id: <20110516.141158.1777924960833804150.davem@davemloft.net> (sfid-20110516_201326_499799_9AE616E6) To: kvalo@adurom.com Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 0/2] Fix uevent race in register_netdevice() From: David Miller In-Reply-To: <20110516143913.13838.85357.stgit@localhost6.localdomain6> References: <20110516143913.13838.85357.stgit@localhost6.localdomain6> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: From: Kalle Valo Date: Mon, 16 May 2011 17:46:30 +0300 > I'm trying to fix a race in register_netdevice(). The problem is that > there's a uevent to userspace before the netdevice is ready for use. The > problem is described here: > > https://bugzilla.kernel.org/show_bug.cgi?id=15606 > > I have sent few different ways to fix this, but none of them have been > really usable. Now I came up with a way which changes the driver core > to make it possible send the uevent in a separate call. This is a clean > and safe way to fix the race. Downside is that two new functions are > added to the driver core interface. > > Please comment. This doesn't work. The sysfs file will still be there before the uevent, so any process can go in there, and see the inconsistent state.