From: Andrew Morton <akpm@linux-foundation.org>
To: NeilBrown <neilb@suse.de>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, adobriyan@gmail.com,
Greg <greg@kroah.com>
Subject: Re: linux-next: Tree for December 9
Date: Tue, 9 Dec 2008 17:58:13 -0800 [thread overview]
Message-ID: <20081209175813.2d847563.akpm@linux-foundation.org> (raw)
In-Reply-To: <16e59424891c03bfe31eb0898fedeac9.squirrel@neil.brown.name>
On Wed, 10 Dec 2008 12:42:58 +1100 (EST) "NeilBrown" <neilb@suse.de> wrote:
> On Wed, December 10, 2008 12:30 pm, Andrew Morton wrote:
> > On Wed, 10 Dec 2008 01:31:13 +0100 "Kay Sievers" <kay.sievers@vrfy.org>
> > 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.
>
> Let's not count our chickens .... :-)
>
> Can you get me
> tar czvf - /lib/udev /etc/udev | mail neilb
>
> so I can see exactly what FC6 is likely to try to do when an
> md device appears or disappears?
Not until tomorrow. The machine is powered off and someone broke
poweroff (again) so I can't WoL it.
next prev parent reply other threads:[~2008-12-10 1:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 7:52 linux-next: Tree for December 9 Stephen Rothwell
2008-12-09 8:53 ` Al Viro
2008-12-09 13:57 ` byteorder headers on parisc Alexey Dobriyan
2008-12-09 23:12 ` Harvey Harrison
2008-12-09 23:34 ` linux-next: Tree for December 9 Andrew Morton
2008-12-10 0:06 ` Kay Sievers
2008-12-10 0:15 ` Andrew Morton
2008-12-10 0:31 ` Kay Sievers
2008-12-10 1:30 ` Andrew Morton
2008-12-10 1:36 ` Kay Sievers
2008-12-10 1:42 ` NeilBrown
2008-12-10 1:58 ` Andrew Morton [this message]
2008-12-10 19:16 ` Andrew Morton
2008-12-10 22:15 ` Neil Brown
2008-12-10 11:57 ` [BUG] linux-next: 20081209 - kernel bug at __rcu_process_callbacks, while booting up Kamalesh Babulal
2008-12-10 14:54 ` Paul E. McKenney
2008-12-10 16:30 ` Kamalesh Babulal
2008-12-10 17:53 ` Paul E. McKenney
2008-12-10 18:09 ` Kamalesh Babulal
2008-12-10 18:33 ` Paul E. McKenney
2008-12-12 19:40 ` Kamalesh Babulal
2008-12-12 22:16 ` Paul E. McKenney
2008-12-16 14:30 ` Kamalesh Babulal
2008-12-16 14:37 ` Jens Axboe
2008-12-17 11:12 ` Kamalesh Babulal
2008-12-17 11:18 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2009-12-09 6:47 linux-next: Tree for December 9 Stephen Rothwell
2010-12-09 4:41 Stephen Rothwell
2010-12-09 11:46 ` Zimny Lech
2010-12-09 15:49 ` Greg KH
2010-12-09 16:42 ` Zimny Lech
2010-12-09 19:35 ` Jing Huang
2010-12-09 20:29 ` Zimny Lech
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081209175813.2d847563.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=neilb@suse.de \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.