linux-kernel - Re: [PATCH] sched: Use show_regs() to improve __schedule

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]

Message-ID: <20071022123506.GB4990@elte.hu>
Date:	Mon, 22 Oct 2007 14:35:06 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Satyam Sharma <satyam@...radead.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sched: Use show_regs() to improve __schedule_bug()
	output


* Satyam Sharma <satyam@...radead.org> wrote:

> BTW would something similar would be useful in __schedule_bug() too? I 
> sure think so -- I'm not sure if EIP holds anything useful there, but 
> CPU#, EFLAGS and the init_utsname() stuff would be definitely helpful 
> ...
> 
> [PATCH] sched: Use show_regs() to improve __schedule_bug() output
> 
> A full register dump along with stack backtrace would make the 
> "scheduling while atomic" message more helpful. Use show_regs() 
> instead of dump_stack() for this. We already know we're atomic in here 
> (that is why this function was called) so show_regs()'s atomicity 
> expectations are guaranteed.
> 
> Also, modify the output of the "BUG: scheduling while atomic:" header 
> a bit to keep task->comm and task->pid together and preempt_count() 
> after them.

thanks, applied.

	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/