[PATCH] Fix fs/locks.c init order

The patch below fixes an interesting oddity we're seeing with fedora core
development (where we recently started using udev heavily); basically right
now filelock_init() is a module_init(), eg runs late.  However that breaks
down because there are earlier /sbin/hotplug callouts, which with udev, do
locking operations.  When that happens the kernel oopses because the slabs
for file locks aren't initialized yet.

Solution: initialize this way early.  It's only a kmem_cache_create after
all, so can happen early.
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

fs/locks.c

@@ -2063,4 +2063,4 @@ static int __init filelock_init(void)
 	return 0;
 }
 
-module_init(filelock_init)
+core_initcall(filelock_init);