linux-kernel - Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in 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 for Android: free password hash cracker in your pocket

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

Date:   Sat, 24 Nov 2018 15:54:02 -1000
From:   Joey Pabalinas <joeypabalinas@...il.com>
To:     Elvira Khabirova <lineprinter@...linux.org>
Cc:     oleg@...hat.com, rostedt@...dmis.org, mingo@...hat.com,
        linux-api@...r.kernel.org, esyr@...hat.com,
        linux-kernel@...r.kernel.org, luto@...nel.org, ldv@...linux.org,
        strace-devel@...ts.strace.io,
        Joey Pabalinas <joeypabalinas@...il.com>
Subject: Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in
 ptrace_message

On Sun, Nov 25, 2018 at 02:22:27AM +0100, Elvira Khabirova wrote:
> Define two constants, PTRACE_EVENTMSG_SYSCALL_ENTRY and
> PTRACE_EVENTMSG_SYSCALL_EXIT, and place them in ptrace_message
> for the duration of syscall-stops.
> This way ptracers can distinguish syscall-enter-stops
> from syscall-exit-stops using PTRACE_GETEVENTMSG request.

Is there an advantage to using two constants instead of a single
sys_exit bit (set/unset for syscall-exit-stop/syscall-enter-stop)?

-- 
Cheers,
Joey Pabalinas

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)