linux-kernel - Re: [x86] BUG: unable to handle kernel NULL pointer dereference at (null)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFyFJMUAADPmGHUVX9OWOt_jN=WhfQ0EBMCY5+LOKxMXqA@mail.gmail.com>
Date:	Tue, 8 Oct 2013 18:33:45 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Richard Henderson <rth@...ddle.net>,
	Jakub Jelinek <jakub@...hat.com>,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: [x86] BUG: unable to handle kernel NULL pointer dereference at (null)

On Tue, Oct 8, 2013 at 6:09 PM, Fengguang Wu <fengguang.wu@...el.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/