Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754922AbYLJBgy (ORCPT ); Tue, 9 Dec 2008 20:36:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751631AbYLJBgp (ORCPT ); Tue, 9 Dec 2008 20:36:45 -0500 Received: from ey-out-2122.google.com ([74.125.78.24]:7551 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750941AbYLJBgo (ORCPT ); Tue, 9 Dec 2008 20:36:44 -0500 Message-ID: Date: Wed, 10 Dec 2008 02:36:42 +0100 From: "Kay Sievers" To: "Andrew Morton" Subject: Re: linux-next: Tree for December 9 Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, adobriyan@gmail.com, Greg , NeilBrown In-Reply-To: <20081209173048.18382f6d.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081209185237.8bb715d7.sfr@canb.auug.org.au> <20081209153418.4628723d.akpm@linux-foundation.org> <20081209161511.15fe8cdb.akpm@linux-foundation.org> <20081209173048.18382f6d.akpm@linux-foundation.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1845 Lines: 48 On Wed, Dec 10, 2008 at 02:30, Andrew Morton wrote: > On Wed, 10 Dec 2008 01:31:13 +0100 "Kay Sievers" wrote: > >> > akpm2:/home/akpm# udevmonitor >> > udevmonitor prints the received event from the kernel [UEVENT] >> > and the event which udev sends out after rule processing [UDEV] >> > >> > UDEV [1228867146.103334] add@/class/bdi/9:0 >> > UDEV [1228867146.107566] remove@/block/md0 >> > UDEV [1228867146.111969] remove@/class/bdi/9:0 >> > UEVENT[1228867146.119889] add@/block/md0 >> > UEVENT[1228867146.119964] add@/class/bdi/9:0 >> > UEVENT[1228867146.120162] remove@/class/bdi/9:0 >> > UEVENT[1228867146.120205] remove@/block/md0 >> > UDEV [1228867146.122839] add@/block/md0 >> > UDEV [1228867146.129125] add@/class/bdi/9:0 >> > UDEV [1228867146.133459] remove@/block/md0 >> > UDEV [1228867146.137813] remove@/class/bdi/9:0 >> > UEVENT[1228867146.145652] add@/block/md0 >> >> Weird loop, something is accessing /dev/md0, i guess, which creates >> the kernel device, and the event, which accesses /dev/md0 again and it >> goes crazy. Maybe caused by changes Neil did. > > I knew an Australian was to blame - it's just a matter of determining > which one. I added him alredy to Cc: with the last mail. :) I guess it's something like this: http://neil.brown.name/git?p=md;a=commitdiff;h=6ac9b8824fd2f82fff508eecc5c74cf797e93cb2 I really hope we can fix that change, as we want to have proper lifetime rules like this, where the devices, which are not used, do not show up. >> Do you use md devices on that box? > > Nope. Fine. Kay -- 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/