linux-kernel - Re: [PATCH 30/31] Add debugger entry points for SPARC

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:	Thu, 28 Jan 2016 14:35:22 -0700
From:	Jeffrey Merkey <jeffmerkey@...il.com>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	linux-kernel@...r.kernel.org, davem@...emloft.net,
	linux.mdb@...il.com, sparclinux@...r.kernel.org
Subject: Re: [PATCH 30/31] Add debugger entry points for SPARC

On 1/28/16, Sam Ravnborg <sam@...nborg.org> wrote:
> Hi Jeff.
>
>> +++ b/arch/sparc/include/asm/kdebug.h
>> @@ -5,4 +5,9 @@
>>  #else
>>  #include <asm/kdebug_32.h>
>>  #endif
>> +
>> +static inline void arch_breakpoint(void)
>> +{
>> +	asm("ta	$0x7d");
>> +}
>>  #endif
> There seems to be some debugger infrastructure present already for kgdb,
> but I assume this cannot be used.
> Anyway - trap 0x7d is a debugger trap in sparc32.
> If CONFIG_KGDB is not defined then 0x7d is just a regular BAD_TRAP.
>
> For sparc64 trap 0x7d is something different.
> I did not conclude what was the right choice for neither.
>
> 	Sam
>

I'll go research that one.  If I am unsure I'll no-op the function for
sparc and let you guys decide how architecturally you wish to handle
that.

:-)

Jeff