linux-kernel - Re: [PATCH] stacktrace: don't crash on invalid stack trace structs

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]

Date:	Mon, 5 May 2008 08:31:17 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Ingo Molnar <mingo@...hat.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] stacktrace: don't crash on invalid stack trace structs


* Johannes Berg <johannes@...solutions.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
--
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/