Re: [x86] BUG: unable to handle kernel NULL pointer dereference at (null)
From: Linus Torvalds
Date: Tue Oct 08 2013 - 21:33:58 EST
On Tue, Oct 8, 2013 at 6:09 PM, Fengguang Wu <fengguang.wu@xxxxxxxxx> wrote:
> [ 27.189229] BUG: unable to handle kernel NULL pointer dereference at 00000108
> [ 27.190165] IP: [<c1109200>] rw_verify_area+0xa0/0x1b0
This looks like file->f_inode is NULL, and it's trying to access inode->i_flock.
There's a number of other ones too (that last delayed __fput one, for
example) that might be due to a NULL inode.
And a lot of thre rest are file-handling too, with the BUG_ON() in
__put_cred() when there's something wrong with file->f_cred.
.. but I have no clue how that could happen and why the asm goto
should matter for this.
Linus
--
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/