linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	jannh@google.com,  Kees Cook <keescook@chromium.org>,
	jeffv@google.com, minchan@kernel.org,  mhocko@suse.com,
	shakeelb@google.com, rientjes@google.com,
	 edgararriaga@google.com, timmurray@google.com,
	linux-mm@kvack.org,  selinux@vger.kernel.org,
	linux-api@vger.kernel.org,  linux-kernel@vger.kernel.org,
	kernel-team@android.com,  linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 1/1] mm/madvise: replace ptrace attach requirement for process_madvise
Date: Wed, 20 Jan 2021 16:01:13 +1100 (AEDT)	[thread overview]
Message-ID: <c586aa93-52d7-bd6c-3d5-77be4ed4afae@namei.org> (raw)
In-Reply-To: <20210111170622.2613577-1-surenb@google.com>

On Mon, 11 Jan 2021, Suren Baghdasaryan wrote:

> Replace PTRACE_MODE_ATTACH with a combination of PTRACE_MODE_READ
> and CAP_SYS_NICE. PTRACE_MODE_READ to prevent leaking ASLR metadata
> and CAP_SYS_NICE for influencing process performance.


Almost missed these -- please cc the LSM mailing list when modifying 
capabilities or other LSM-related things.

-- 
James Morris
<jmorris@namei.org>



  parent reply	other threads:[~2021-01-20  5:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 17:06 [PATCH v2 1/1] mm/madvise: replace ptrace attach requirement for process_madvise Suren Baghdasaryan
2021-01-11 18:33 ` Kees Cook
2021-01-12  1:22 ` Andrew Morton
2021-01-12 17:36   ` Suren Baghdasaryan
2021-01-12  7:46 ` Michal Hocko
2021-01-12 17:45   ` Oleg Nesterov
2021-01-12 17:51     ` Suren Baghdasaryan
2021-01-13 14:22       ` Michal Hocko
2021-01-13 18:08         ` Suren Baghdasaryan
2021-01-20 13:17         ` Jann Horn
2021-01-20 16:57           ` Suren Baghdasaryan
2021-01-20 20:46             ` Suren Baghdasaryan
2021-01-26 13:52           ` Michal Hocko
2021-01-28 19:51             ` Suren Baghdasaryan
2021-01-29  7:08               ` Suren Baghdasaryan
2021-02-02  5:34                 ` Suren Baghdasaryan
     [not found]                   ` <CAJuCfpEOE8=L1fT4FSauy65cS82M_kW3EzTgH89ewE9HudL=VA@mail.gmail.com>
2021-03-03  0:17                     ` Andrew Morton
2021-03-03  0:19                       ` Suren Baghdasaryan
2021-03-03 19:00                         ` Suren Baghdasaryan
2021-01-12 18:12   ` Suren Baghdasaryan
2021-01-13 14:19     ` Michal Hocko
2021-01-20  5:01 ` James Morris [this message]
2021-01-20 16:49   ` Suren Baghdasaryan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c586aa93-52d7-bd6c-3d5-77be4ed4afae@namei.org \
    --to=jmorris@namei.org \
    --cc=akpm@linux-foundation.org \
    --cc=edgararriaga@google.com \
    --cc=jannh@google.com \
    --cc=jeffv@google.com \
    --cc=keescook@chromium.org \
    --cc=kernel-team@android.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=rientjes@google.com \
    --cc=selinux@vger.kernel.org \
    --cc=shakeelb@google.com \
    --cc=surenb@google.com \
    --cc=timmurray@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).