linux-kernel - Re: [PATCH] Info dump on Oops or panic()

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070628221835.GI2784@fattire.cabal.ca>
Date:	Thu, 28 Jun 2007 18:18:35 -0400
From:	Kyle McMartin <kyle@...artin.ca>
To:	Joshua Wise <jwise@...gle.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...gle.com, thockin@...gle.com,
	mikew@...gle.com, masouds@...gle.com
Subject: Re: [PATCH] Info dump on Oops or panic()

On Thu, Jun 28, 2007 at 03:05:56PM -0700, Joshua Wise wrote:
> --- a/arch/x86_64/kernel/process.c
> +++ b/arch/x86_64/kernel/process.c
> @@ -356,6 +356,7 @@ void show_regs(struct pt_regs *regs)
>  	printk("CPU %d:", smp_processor_id());
>  	__show_regs(regs);
>  	show_trace(NULL, regs, (void *)(regs + 1));
> +	atomic_notifier_call_chain(&info_dumper_list, 0, NULL);
>  }
> 

woah woah woah. This could push critical bits of the register dump or
stacktrace off the screen... Barring any other problems with the patch,
this should probably be dumped in the oops header, not trailing it where
it could hide critical debugging info.

Regards,
	Kyle M.
-
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/