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:	Tue, 31 Oct 2006 17:48:12 +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: Fri, 27 Oct 2006 12:50:29 +0530
>
>  
>
>>    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.
>>    
>>
>
>Yep.  Are the no current users at all?  That's strange...
>  
>
David,
I guess the reasons for its less (or no) usage could be
1. These options are not documented in manpage
2. The usage is different from the general format of ptrace
3.  These are used for copying all the registers. Most applications will 
require data from a single addr/register at a time and can get this data 
from a specific register/address using PEEKTEXT or POKETEXT.

We could align these options with the general format of ptrace and then 
document in manpage mentioning the relevant kernel version

(like what we have for PTRACE_O_TRACESYSGOOD in which kernel version is 
mentioned)
PTRACE_O_TRACESYSGOOD (since Linux 2.4.6)

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ