From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f65.google.com ([209.85.218.65]:34875 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751980AbcKAX5G (ORCPT ); Tue, 1 Nov 2016 19:57:06 -0400 MIME-Version: 1.0 In-Reply-To: <1477863998-3298-1-git-send-email-jann@thejh.net> References: <1477863998-3298-1-git-send-email-jann@thejh.net> From: Linus Torvalds Date: Tue, 1 Nov 2016 17:57:05 -0600 Message-ID: Subject: Re: [PATCH v3 0/8] Various fixes related to ptrace_may_access() To: Jann Horn Cc: Alexander Viro , Roland McGrath , Oleg Nesterov , John Johansen , James Morris , "Serge E. Hallyn" , Paul Moore , Stephen Smalley , Eric Paris , Casey Schaufler , Kees Cook , Andrew Morton , Janis Danisevskis , Seth Forshee , "Eric W. Biederman" , Thomas Gleixner , Benjamin LaHaise , Ben Hutchings , Andy Lutomirski , Krister Johansen , linux-fsdevel , LSM List , "security@kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Oct 30, 2016 at 3:46 PM, Jann Horn wrote: > Next try. > > Changes to the individual patches are mostly documented in their > commit messages. > > Added/removed patches: > - Added "proc: fix timerslack_ns handling" > - Removed "ptrace: warn on ptrace_may_access without proper locking" > (because of some reverted changes in the "proc: lock properly [...]" > patch) So I'm a bit unsure which tree this series is going to come in through. There's no clear maintinership for this area, so I'm just making sure that Andrew has this on his radar because I suspect this is going to fall in his lap. Oleg, you're really the obvious maintainer choice at least for some of this, but I don't recall having ever pulled from you? If you are ok with this and were to put git tree etc, that would certainly also work very well. Or at least ack's for Andrew? Linus --- > Jann Horn (8): > exec: introduce cred_guard_light > exec: add privunit to task_struct > proc: use open()-time creds for ptrace checks > futex: don't leak robust_list pointer > proc: lock properly in ptrace_may_access callers > fs/proc: fix attr access check > proc: fix timerslack_ns handling > Documentation: add security/ptrace_checks.txt