linux-kernel - Re: [patch 2/2] Add the end-of-trace marker and the module list to WARN

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]

Date:	Fri, 4 Jan 2008 11:43:22 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	olof@...om.net
Subject: Re: [patch 2/2] Add the end-of-trace marker and the module list to
	WARN_ON()


* Arjan van de Ven <arjan@...ux.intel.com> wrote:

> Ingo Molnar wrote:
>> * Arjan van de Ven <arjan@...ux.intel.com> wrote:
>>
>>> +	printk(KERN_WARNING "------------[ cut here ]------------\n");
>>>  	printk(KERN_WARNING "WARNING: at %s:%d %s()\n", file,
>>>  		line, function);
>>> +	print_modules();
>>>  	dump_stack();
>>> +	print_oops_end_marker();
>>
>> another thing: could we also put the marker into dump_stack(), and attach 
>> the marker to the Call Trace line?
>
> I have a preliminary patch for that already but I'm not happy with it 
> yet; I need to redo it properly. It's neither depending nor 
> incremental to these 2 patches though..

yeah, it was a sidenote - it should be separate to these two patches.

	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/