x86/ptrace: Stop setting TS_COMPAT in ptrace code
Setting TS_COMPAT in ptrace is wrong: if we happen to do it during syscall entry, then we'll confuse seccomp and audit. (The former isn't a security problem: seccomp is currently entirely insecure if a malicious ptracer is attached.) As a minimal fix, this patch adds a new flag TS_I386_REGS_POKED that handles the ptrace special case. Signed-off-by:Andy Lutomirski <luto@kernel.org> Acked-by:
Oleg Nesterov <oleg@redhat.com> Cc: Borislav Petkov <bp@alien8.de> Cc: Brian Gerst <brgerst@gmail.com> Cc: Denys Vlasenko <dvlasenk@redhat.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Josh Poimboeuf <jpoimboe@redhat.com> Cc: Kees Cook <keescook@chromium.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Pedro Alves <palves@redhat.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/5383ebed38b39fa37462139e337aff7f2314d1ca.1469599803.git.luto@kernel.org Signed-off-by:
Ingo Molnar <mingo@kernel.org>
parent
37e13a1e
-
mentioned in commit 591d6c21
-
mentioned in commit c6159407
-
mentioned in commit 400e3df4
-
mentioned in commit 1454a47f
-
mentioned in commit 6cd1e198
-
mentioned in commit 2c79ceee
-
mentioned in commit 376a76aa
-
mentioned in commit 5b871095
-
mentioned in commit 4a3b8246
-
mentioned in commit 922bfc31
-
mentioned in commit def9b93d
-
mentioned in commit 3704f0a6
-
mentioned in commit 27ddd2b5
-
mentioned in commit de2e1603
-
mentioned in commit 076b60af
-
mentioned in commit a548acde
-
mentioned in commit 4523e648
-
mentioned in commit 97c60895
Please register or sign in to comment