linux-next: boot failure

From: Stephen Rothwell
Date: Wed Jul 01 2009 - 02:00:33 EST


Hi Eric,

next-20090630 failed to boot (on PowerPC Power5/6 machines):

calling .audit_watch_init+0x0/0x80 @ 1
Unable to handle kernel paging request for data at address 0xffffffffffffffff
Faulting instruction address: 0xc00000000008b440
cpu 0x0: Vector: 300 (Data Access) at [c0000000be683990]
pc: c00000000008b440: .srcu_read_lock+0x20/0x40
lr: c0000000001607cc: .fsnotify_recalc_global_mask+0x2c/0xa0
sp: c0000000be683c10
msr: 8000000000009032
dar: ffffffffffffffff
dsisr: 40010000
current = 0xc0000000be67e000
paca = 0xc00000000093b200
pid = 1, comm = swapper
enter ? for help
[link register ] c0000000001607cc .fsnotify_recalc_global_mask+0x2c/0xa0
[c0000000be683c10] c0000000be683ca0 (unreliable)
[c0000000be683ca0] c000000000160bc0 .fsnotify_obtain_group+0x1e0/0x260
[c0000000be683d60] c0000000007879e4 .audit_watch_init+0x34/0x80
[c0000000be683de0] c00000000000947c .do_one_initcall+0x6c/0x1e0
[c0000000be683ee0] c00000000076fd6c .kernel_init+0x23c/0x2c0
[c0000000be683f90] c00000000002a9bc .kernel_thread+0x54/0x70

next-20090629 was fine. The commits in 0630 and not in 0629 (from the
fsnotify tree) are:

Audit: clean up the audit_watch split
audit: convert audit watches to use fsnotify instead of inotify
audit: redo audit watch locking and refcnt in light of fsnotify
audit: do not get and put just to free a watch
fsnotify: duplicate fsnotify_mark_entry data between 2 marks
fsnotify: allow addition of duplicate fsnotify marks
audit: reimplement audit_trees using fsnotify rather than inotify
inotify: deprecate the inotify kernel interface

If I have time, I may do a bisection.
--
Cheers,
Stephen Rothwell sfr@xxxxxxxxxxxxxxxx
http://www.canb.auug.org.au/~sfr/

Attachment: pgp00000.pgp
Description: PGP signature