linux-kernel - Re: [PATCH v4 4/4] pr_emerg add 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 2 Feb 2016 19:40:48 +0000 (GMT)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Jeffrey Merkey <jeffmerkey@...il.com>
cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	Jason@...c4.com, aconole@...hat.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	andriy.shevchenko@...ux.intel.com, linus.walleij@...aro.org,
	nicolas.iooss_linux@....org, pmladek@...e.com, tj@...nel.org
Subject: Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options

On Mon, 1 Feb 2016, Jeffrey Merkey wrote:

> If a debugger is loaded it will not crash, just enter the debugger.
> But yes, it will int3 if set and no debugger has been loaded to handle
> the int3 condition.  Hmmm.  Maybe its better just to skip calling
> pr_emerg and put this logic as a single call somewhere else.

 What's the point?  If you have a debugger loaded, then surely you can 
just set a breakpoint anywhere you like using whatever user interface the 
debugger provides for setting breakpoints.  You can actually set any 
number of software breakpoints you like wherever you like, depending on 
what you actually want to debug.  I fail to see why it would have to be 
prearranged within the kernel -- do you have a configuration where you run 
the kernel from ROM by any chance?

  Maciej