[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXu5jJtWJ=hhMVg7u28gEGOq3ue1f_phxZ-GTF0sfV5EgVoBw@mail.gmail.com>
Date: Tue, 10 Sep 2013 15:44:57 -0700
From: Kees Cook <keescook@...omium.org>
To: Andrew Morton <akpm@...ux-foundation.org>,
Tony Luck <tony.luck@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Stephen Boyd <sboyd@...eaurora.org>,
Vikram Mulukutla <markivx@...eaurora.org>,
Peter Zijlstra <peterz@...radead.org>,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH] panic: call panic handlers before kmsg_dump
On Tue, Sep 10, 2013 at 3:41 PM, Kees Cook <keescook@...omium.org> wrote:
> On Thu, Jul 18, 2013 at 4:17 PM, Tony Luck <tony.luck@...il.com> wrote:
>> On Thu, Jul 18, 2013 at 4:03 PM, Kees Cook <keescook@...omium.org> wrote:
>>> Since the panic handlers may produce additional information (via printk)
>>> for the kernel log, it should be reported as part of the panic output
>>> saved by kmsg_dump(). Without this re-ordering, nothing that adds
>>> information to a panic will show up in pstore's view when kmsg_dump
>>> runs, and is therefore not visible to crash reporting tools that examine
>>> pstore output.
>>
>> Good point.
>>
>> Acked-by: Tony Luck <tony.luck@...el.com>
>
> Can someone pick this patch up? If akpm doesn't want it, it could live
> in the pstore tree maybe?
Ah, sorry, it seems like it is already in -mm. Never mind!
-Kees
--
Kees Cook
Chrome OS Security
--
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/
Powered by blists - more mailing lists