linux-kernel - Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE

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: <4541B33D.6090704@in.ibm.com>
Date:	Fri, 27 Oct 2006 12:50:29 +0530
From:	supriya kannery <supriyak@...ibm.com>
To:	David Miller <davem@...emloft.net>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Incorrect order of last two arguments of ptrace for requests
 PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS

David Miller wrote:

>From: supriya kannery <supriyak@...ibm.com>
>Date: Wed, 25 Oct 2006 16:23:14 +0530
>
>  
>
>>If we exchange the last two arguments like,
>>
>> ptrace (PPC_PTRACE_GETREGS, pid, &reg[0], 0);
>>
>>it works!
>>    
>>
>
>Please make sure that programs, such as gdb, aren't using the reversed
>argument order.  If they are, you cannot "fix" this as it will break
>all such applictions.
>  
>
David,
    I checked in gdb and ltrace code. None of them are using PPC_PTRACE* 
options to get register values.
Man page also doesn't mention these options. Once this is fixed, these 
options could be added to man page also.

Irrespective of whether we fix this, documentation of these options in 
manpage will clarify its usage I guess.
Thanks, Supriya
-
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/