From: Ingo Molnar <mingo@elte.hu>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ingo Molnar <mingo@redhat.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] stacktrace: don't crash on invalid stack trace structs
Date: Mon, 5 May 2008 08:31:17 +0200 [thread overview]
Message-ID: <20080505063117.GA3350@elte.hu> (raw)
In-Reply-To: <1209904761.4065.19.camel@johannes.berg>
* Johannes Berg <johannes@sipsolutions.net> wrote:
> This patch makes the stacktrace printout code warn when the entries
> pointer is unset rather than crashing when trying to access it in an
> attempt to make it a bit more robust.
>
> I was saving a stacktrace into an skb and forgot to copy it across skb
> copies... Not sure if you want this, I have since fixed the code, but
> it would have been easier had the kernel not crashed in an interrupt.
applied, thanks Johannes.
I agree that such code needs to be more resilient, and resilience is
mainly driven by observing random incidents as they happen in the field.
So please keep sending such patches (even if they might seem dubious to
you at first sight), they do make a lot of sense - and even if a patch
does not end up getting applied your submission documents the incident.
Ingo
prev parent reply other threads:[~2008-05-05 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 12:39 Johannes Berg
2008-05-05 6:31 ` Ingo Molnar [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=20080505063117.GA3350@elte.hu \
--to=mingo@elte.hu \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®