Bug#618340: BUG: unable to handle kernel NULL pointer dereference at (null) w/ BTRFS

[Mikko Ylinen <mikko.k.ylinen@iki.fi>]

On Sun, 22 May 2011, Moritz Muehlenhoff wrote:

> > [  666.971952] Call Trace:
> > [  666.971979]  [<c108c1e0>] ? iov_iter_copy_from_user_atomic+0x26/0x5e
> > [  666.972008]  [<f85ae97c>] ? btrfs_copy_from_user+0x50/0x8c [btrfs]
> > [  666.972008]  [<f85b098a>] ? btrfs_file_aio_write+0x5c9/0x8fb [btrfs]
> > [  666.972008]  [<c10a2878>] ? do_wp_page+0x5fd/0x61d
> > [  666.972008]  [<c10b9ca3>] ? do_sync_write+0x9e/0xd3
> > [  666.972008]  [<c10b9e78>] ? rw_verify_area+0xcd/0xe7
> > [  666.972008]  [<c10b9c05>] ? do_sync_write+0x0/0xd3
> > [  666.972008]  [<c10ba21d>] ? vfs_write+0x7f/0xd9
> > [  666.972008]  [<c10ba30a>] ? sys_write+0x3c/0x60
> > [  666.972008]  [<c12881bc>] ? syscall_call+0x7/0xb
> >
> > Maybe related? https://bugzilla.kernel.org/show_bug.cgi?id=26242
>
> 3a90983dbdcb2f4f48c0d771d8e5b4d88f27fae6 was released with 2.6.38,
> can you confirm that it's fixed in the current testing/sid kernels?

I haven't seen this bug anymore.

--
Regards, Mikko