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  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:   Sat, 2 Mar 2019 17:11:40 -0800
From:   Andy Lutomirski <>
To:     Sudeep Holla <>
Cc:     X86 ML <>,
        linux-arm-kernel <>,
        LKML <>,
        linuxppc-dev <>,
        Catalin Marinas <>,
        Will Deacon <>,
        Oleg Nesterov <>,
        Paul Mackerras <>,
        Michael Ellerman <>,
        Thomas Gleixner <>,
        Ingo Molnar <>,
        Richard Weinberger <>,
        Jeff Dike <>,
        Steve Capper <>,
        Haibo Xu <>, Bin Lu <>,
        Andy Lutomirski <>,
        Borislav Petkov <>
Subject: Re: [PATCH 3/6] x86: clean up _TIF_SYSCALL_EMU handling using
 ptrace_syscall_enter hook

On Thu, Feb 28, 2019 at 10:32 AM Sudeep Holla <> wrote:
> Now that we have a new hook ptrace_syscall_enter that can be called from
> syscall entry code and it handles PTRACE_SYSEMU in generic code, we
> can do some cleanup using the same in syscall_trace_enter.
> Further the extra logic to find single stepping PTRACE_SYSEMU_SINGLESTEP
> in syscall_slow_exit_work seems unnecessary. Let's remove the same.

I wasn't cc'd on the whole series, so I can't easily review this.  Do
you have a test case to make sure that emulation still works?  Are
there adequate tests in tools/testing/selftests/x86?  Do they still
pass after this patch?


Powered by blists - more mailing lists