From: Daniel Thompson <daniel.thompson@linaro.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
patches@linaro.org, linaro-kernel@lists.linaro.org,
John Stultz <john.stultz@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [PATCH RESEND 3.18-rc3 v2 1/2] trace: kdb: Fix kernel panic during ftdump
Date: Fri, 14 Nov 2014 09:08:21 +0000 [thread overview]
Message-ID: <5465C685.9060006@linaro.org> (raw)
In-Reply-To: <20141113212646.6d720886@gandalf.local.home>
On 14/11/14 02:26, Steven Rostedt wrote:
> On Thu, 6 Nov 2014 12:41:55 +0000
> Daniel Thompson <daniel.thompson@linaro.org> wrote:
>
>> Currently kdb's ftdump command unconditionally crashes due to a null
>> pointer de-reference whenever the command is run. This in turn causes
>> the kernel to panic.
>>
>> The abridged stacktrace (gathered with ARCH=arm) is:
>> --- cut here ---
>
> This is a nasty line. "git am " truncated the change log there thinking
> it was the end of the change log (that '---' did it).
Oops. Looks like I shall have to train myself out of that particular
habit (which will be tough, since I've used it long enough to be ingrained).
Will repost as soon as I've thought about your other comments.
Daniel.
next prev parent reply other threads:[~2014-11-14 9:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 14:44 [PATCH 3.17-rc4] trace: kdb: Fix kernel panic during ftdump Daniel Thompson
2014-09-24 10:32 ` [PATCH 3.17-rc4 v2 0/2] trace: kdb: Bug fixes for ftdump Daniel Thompson
2014-09-24 10:33 ` [PATCH 3.17-rc4 v2 1/2] trace: kdb: Fix kernel panic during ftdump Daniel Thompson
2014-09-24 10:33 ` [PATCH 3.17-rc4 v2 2/2] trace: kdb: Fix kernel livelock with empty buffers Daniel Thompson
2014-09-24 15:07 ` [PATCH 3.17-rc4 v2 0/2] trace: kdb: Bug fixes for ftdump Steven Rostedt
2014-09-24 15:09 ` Daniel Thompson
2014-11-06 12:41 ` [PATCH RESEND 3.18-rc3 " Daniel Thompson
2014-11-06 12:41 ` [PATCH RESEND 3.18-rc3 v2 1/2] trace: kdb: Fix kernel panic during ftdump Daniel Thompson
2014-11-14 2:26 ` Steven Rostedt
2014-11-14 9:08 ` Daniel Thompson [this message]
2014-11-14 11:59 ` Steven Rostedt
2014-11-14 12:13 ` Daniel Thompson
2014-11-14 12:31 ` Steven Rostedt
2014-11-14 12:35 ` Steven Rostedt
2014-11-06 12:41 ` [PATCH RESEND 3.18-rc3 v2 2/2] trace: kdb: Fix kernel livelock with empty buffers Daniel Thompson
2014-11-06 13:27 ` [PATCH RESEND 3.18-rc3 v2 0/2] trace: kdb: Bug fixes for ftdump Steven Rostedt
2014-11-10 9:41 ` Daniel Thompson
2014-11-14 2:16 ` Steven Rostedt
2014-11-14 11:03 ` Daniel Thompson
2014-11-14 11:21 ` [PATCH 3.18-rc3 v3 " Daniel Thompson
2014-11-14 11:21 ` [PATCH 3.18-rc3 v3 1/2] trace: kdb: Fix kernel panic during ftdump Daniel Thompson
2014-11-14 11:21 ` [PATCH 3.18-rc3 v3 2/2] trace: kdb: Fix kernel livelock with empty buffers Daniel Thompson
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=5465C685.9060006@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=jason.wessel@windriver.com \
--cc=john.stultz@linaro.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patches@linaro.org \
--cc=rostedt@goodmis.org \
--cc=sumit.semwal@linaro.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