From: David Howells <dhowells@redhat.com>
To: zer0mem@yahoo.com
Cc: dhowells@redhat.com, Greg KH <gregkh@linuxfoundation.org>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
"keyrings@vger.kernel.org" <keyrings@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [zer0mem@yahoo.com: [oss-security] panic at big_key_preparse #4.7-r6/rc7 & master]
Date: Tue, 26 Jul 2016 08:45:04 +0100 [thread overview]
Message-ID: <26504.1469519104@warthog.procyon.org.uk> (raw)
In-Reply-To: <47074.85917.bm@smtp228.mail.bf1.yahoo.com>
<zer0mem@yahoo.com> wrote:
> If you will have no luck to repro issue, I will take a deeper look at it at
> Friday and let you know asap
Can you find out the line on which the crash happens? Load vmlinux into gdb
and do:
i li *0x<RIP-address-from-panic>
If it says it's in some header file somewhere in an inline function, try
decrementing the RIP value until it appears in a C file.
Thanks,
David
next prev parent reply other threads:[~2016-07-26 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 21:41 [zer0mem@yahoo.com: [oss-security] panic at big_key_preparse #4.7-r6/rc7 & master] Greg KH
2016-07-25 13:00 ` David Howells
[not found] ` <531421.11642.bm@smtp201.mail.bf1.yahoo.com>
2016-07-25 21:45 ` David Howells
[not found] ` <47074.85917.bm@smtp228.mail.bf1.yahoo.com>
2016-07-26 7:45 ` David Howells [this message]
2016-07-26 9:17 ` Vegard Nossum
2016-07-26 10:12 ` David Howells
2016-07-25 13:06 ` David Howells
2016-07-25 15:27 ` David Howells
2016-07-25 20:17 ` Greg KH
2016-07-26 22:45 ` David Howells
2016-08-25 22:08 ` Kirill Marinushkin
2016-07-27 13:23 ` [RFC][PATCH] KEYS: Sort out big_key initialisation David Howells
2016-08-11 19:48 ` Kirill Marinushkin
2016-08-27 10:22 ` [zer0mem@yahoo.com: [oss-security] panic at big_key_preparse #4.7-r6/rc7 & master] Kirill Marinushkin
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=26504.1469519104@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.l.morris@oracle.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=zer0mem@yahoo.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