linux-kernel - Re: ptrace 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] [day] [month] [year] [list]

Date:	Mon,  5 May 2008 12:04:18 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Anoop <acv@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: ptrace PTRACE_PEEKUSER behavior

'struct user' is really a virtual structure layout, and never exists
anywhere as an actual struct.  It's really just defining the argument
values that can be used in PEEKUSR/POKEUSR calls.  Its details are
completely machine-specific.  On x86, only the user_regs_struct parts at
the beginning, and the u_debugreg parts near the end, are offsets that are
valid in ptrace calls.  The other elements in x86's 'struct user' are just
historical cruft now.  Any documentation of the details would have to be
given for all the different arch layouts.

Thanks,
Roland
--
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/