From: pebolle@tiscali.nl (Paul Bolle)
To: kernelnewbies@lists.kernelnewbies.org
Subject: BUG: unable to handle kernel NULL pointer dereference at (null)
Date: Thu, 23 Oct 2014 11:05:52 +0200 [thread overview]
Message-ID: <1414055152.17121.25.camel@x220> (raw)
In-Reply-To: <CAGXs5wXPpJpSyUeJ4CVHrgaWoqqWpd9O+f-eTUA+X5UPC==GjQ@mail.gmail.com>
On Thu, 2014-10-23 at 09:58 +0300, Kevin Wilson wrote:
> I am getting this message when running a patched kernel:
> BUG: unable to handle kernel NULL pointer dereference at (null)
That is just what you get when the kernel dereferences NULL, isn't it?
(If the kernel dereferences, say, something halfway some struct, you'll
see a hex address instead of "(null)".) Assuming x86, see:
arch/x86/mm/fault.c:show_fault_oops() and lib/vsprintf.c:pointer().
> Is there some kernel configuration item which enables getting
> , instead "(null)", the proper value (I assume it should be a method name)
Doesn't your BUG also print a backtrace that points at a (possible)
culprit?
Paul Bolle
prev parent reply other threads:[~2014-10-23 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 6:58 BUG: unable to handle kernel NULL pointer dereference at (null) Kevin Wilson
2014-10-23 9:05 ` Paul Bolle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1414055152.17121.25.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).