linux-kernel - Re: segmentation fault running under kgdb

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] [day] [month] [year] [list]

Message-ID: <4D46CEBA.6030508@windriver.com>
Date:	Mon, 31 Jan 2011 09:01:14 -0600
From:	Jason Wessel <jason.wessel@...driver.com>
To:	Kallol Biswas <nucleodyne@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: segmentation fault running under kgdb

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.
--
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/