On Tue, Sep 10, 2013 at 3:41 PM, Kees Cook wrote:
> On Thu, Jul 18, 2013 at 4:17 PM, Tony Luck wrote:
>> On Thu, Jul 18, 2013 at 4:03 PM, Kees Cook wrote:
>>> Since the panic handlers may produce additional information (via printk)
>>> for the kernel log, it should be reported as part of the pan
On Thu, Jul 18, 2013 at 4:17 PM, Tony Luck wrote:
> On Thu, Jul 18, 2013 at 4:03 PM, Kees Cook 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-order
On Thu, Jul 18, 2013 at 4:03 PM, Kees Cook 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 sho
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
4 matches
Mail list logo
