Re: 2.6.16-rc5-mm1

[Andrew Morton]

Laurent Riffard <laurent.riffard@xxxxxxx> wrote:
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address 00000034

I booted that thing on five machines, four architectures :(

Could people please test a couple more patchsets, see if we can isolate it?

http://www.zip.com.au/~akpm/linux/patches/stuff/2.6.16-rc5-mm1.1.gz

is 2.6.16-rc5-mm1 minus:

proc-make-proc_numbuf-the-buffer-size-for-holding-a.patch
tref-implement-task-references.patch
proc-dont-lock-task_structs-indefinitely.patch
proc-dont-lock-task_structs-indefinitely-git-nfs-fix.patch
proc-dont-lock-task_structs-indefinitely-cpuset-fix.patch
proc-optimize-proc_check_dentry_visible.patch

and http://www.zip.com.au/~akpm/linux/patches/stuff/2.6.16-rc5-mm1.2.gz is
2.6.16-rc5-mm1 minus:

trivial-cleanup-to-proc_check_chroot.patch
proc-fix-the-inode-number-on-proc-pid-fd.patch
proc-remove-useless-bkl-in-proc_pid_readlink.patch
proc-remove-unnecessary-and-misleading-assignments.patch
proc-simplify-the-ownership-rules-for-proc.patch
proc-replace-proc_inodetype-with-proc_inodefd.patch
proc-remove-bogus-proc_task_permission.patch
proc-kill-proc_mem_inode_operations.patch
proc-properly-filter-out-files-that-are-not-visible.patch
proc-fix-the-link-count-for-proc-pid-task.patch
proc-move-proc_maps_operations-into-task_mmuc.patch
dcache-add-helper-d_hash_and_lookup.patch
proc-rewrite-the-proc-dentry-flush-on-exit.patch
proc-close-the-race-of-a-process-dying-durning.patch
proc-refactor-reading-directories-of-tasks.patch
#
proc-make-proc_numbuf-the-buffer-size-for-holding-a.patch
tref-implement-task-references.patch
proc-dont-lock-task_structs-indefinitely.patch
proc-dont-lock-task_structs-indefinitely-git-nfs-fix.patch
proc-dont-lock-task_structs-indefinitely-cpuset-fix.patch
proc-optimize-proc_check_dentry_visible.patch


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