Re: [PATCH RESEND 3.18-rc3 v2 1/2] trace: kdb: Fix kernel panic during ftdump
From: Steven Rostedt
Date: Fri Nov 14 2014 - 06:59:33 EST
On Fri, 14 Nov 2014 09:08:21 +0000
Daniel Thompson <daniel.thompson@xxxxxxxxxx> wrote:
> On 14/11/14 02:26, Steven Rostedt wrote:
> > On Thu, 6 Nov 2014 12:41:55 +0000
> > Daniel Thompson <daniel.thompson@xxxxxxxxxx> 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.
I was just telling you so that you wouldn't do it again. I already
pulled in your patches. You didn't need to resend. But at least it
would help you get out of that habit! J
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/