From: Jason Wessel <jason.wessel@windriver.com>
To: Kallol Biswas <nucleodyne@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: segmentation fault running under kgdb
Date: Mon, 31 Jan 2011 09:01:14 -0600 [thread overview]
Message-ID: <4D46CEBA.6030508@windriver.com> (raw)
In-Reply-To: <AANLkTi=FzQPkt1pogJ7BdEtF_nUgTZU5_u3RBX1v0_R2@mail.gmail.com>
On 01/29/2011 08:30 PM, Kallol Biswas wrote:
>
> Here is the stack trace:
> (gdb) bt
> #0 kref_put (kref=0xffffffffffffffc9, release=0xffffffff8127b560
> <aa_free_profile_kref>) at lib/kref.c:67
> #1 0xffffffff8127b069 in aa_put_profile (udata=0xffff8801b7600000,
> size=<value optimized out>, add_only=<value optimized out>) at
> security/apparmor/include/policy.h:295
I have no idea about how apparmor works, but this looks like a legitimate kernel crash and kgdb is catching, just as I would expect. If you want to continue on and pass the signal to the kernel's die notification system at the gdb prompt enter:
signal 9
I would recommend understanding the cause of each crash because because any null dereferences would lead me to wonder about the stability of the kernel you are running.
Jason.
prev parent reply other threads:[~2011-01-31 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 2:30 segmentation fault running under kgdb Kallol Biswas
2011-01-31 15:01 ` Jason Wessel [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=4D46CEBA.6030508@windriver.com \
--to=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nucleodyne@gmail.com \
/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