linux-kernel - Re: linux-next: Tree for December 9

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081209175813.2d847563.akpm@linux-foundation.org>
Date:	Tue, 9 Dec 2008 17:58:13 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"NeilBrown" <neilb@...e.de>
Cc:	"Kay Sievers" <kay.sievers@...y.org>, sfr@...b.auug.org.au,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	adobriyan@...il.com, "Greg" <greg@...ah.com>
Subject: Re: linux-next: Tree for December 9

On Wed, 10 Dec 2008 12:42:58 +1100 (EST) "NeilBrown" <neilb@...e.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@...y.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@...ass/bdi/9:0
> >> > UDEV  [1228867146.107566] remove@...ock/md0
> >> > UDEV  [1228867146.111969] remove@...ass/bdi/9:0
> >> > UEVENT[1228867146.119889] add@...ock/md0
> >> > UEVENT[1228867146.119964] add@...ass/bdi/9:0
> >> > UEVENT[1228867146.120162] remove@...ass/bdi/9:0
> >> > UEVENT[1228867146.120205] remove@...ock/md0
> >> > UDEV  [1228867146.122839] add@...ock/md0
> >> > UDEV  [1228867146.129125] add@...ass/bdi/9:0
> >> > UDEV  [1228867146.133459] remove@...ock/md0
> >> > UDEV  [1228867146.137813] remove@...ass/bdi/9:0
> >> > UEVENT[1228867146.145652] add@...ock/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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/