All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Stanislav Kinsburskiy <skinsbursky@virtuozzo.com>
Cc: "mguzik@redhat.com" <mguzik@redhat.com>,
	"ebiederm@xmission.com" <ebiederm@xmission.com>,
	Pavel Emelianov <xemul@virtuozzo.com>,
	"mhocko@suse.com" <mhocko@suse.com>,
	"matthltc@us.ibm.com" <matthltc@us.ibm.com>,
	"luto@amacapital.net" <luto@amacapital.net>,
	"keescook@chromium.org" <keescook@chromium.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"john.stultz@linaro.org" <john.stultz@linaro.org>,
	"bsegall@google.com" <bsegall@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"gorcunov@openvz.org" <gorcunov@openvz.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"vbabka@suse.cz" <vbabka@suse.cz>,
	"mingo@redhat.com" <mingo@redhat.com>
Subject: Re: [PATCH] prctl: remove one-shot limitation for changing exe link
Date: Wed, 13 Jul 2016 12:15:05 +0200	[thread overview]
Message-ID: <20160713101504.GB6569@redhat.com> (raw)
In-Reply-To: <1d254efe-5410-40c4-af4b-9e898682d0b3@email.android.com>

On 07/12, Stanislav Kinsburskiy wrote:
>
> Thank you for the explanation.
> So, if I understand you right, the patch should be left as it is.
> Is this statement correct?

Yes, yes, feel free to add my ack.

Oleg.

       reply	other threads:[~2016-07-13 10:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1d254efe-5410-40c4-af4b-9e898682d0b3@email.android.com>
2016-07-13 10:15 ` Oleg Nesterov [this message]
2016-07-12 15:42 [PATCH] prctl: remove one-shot limitation for changing exe link Stanislav Kinsburskiy
  -- strict thread matches above, loose matches on Subject: below --
2016-07-12 15:30 Stanislav Kinsburskiy
2016-07-12 16:42 ` Oleg Nesterov
2016-07-12 16:52   ` Stanislav Kinsburskiy
2016-07-12 17:01     ` Oleg Nesterov
2016-07-12 16:48 ` Cyrill Gorcunov
2016-07-12 16:52   ` Eric W. Biederman
2016-07-12 17:29     ` Cyrill Gorcunov
2016-07-12 21:42       ` Cyrill Gorcunov
2016-07-13 10:47     ` Stanislav Kinsburskiy
2016-07-18 20:11     ` One Thousand Gnomes
2016-07-20 11:30       ` Stanislav Kinsburskiy
     [not found] ` <8a863273-c571-63d6-c0c3-637dff5645a3@virtuozzo.com>
2016-07-25 18:21   ` Eric W. Biederman
2016-07-25 19:22     ` Cyrill Gorcunov
2016-07-25 19:56       ` Eric W. Biederman
2016-07-26  8:34         ` Cyrill Gorcunov
2016-07-30 17:31           ` Eric W. Biederman
2016-07-30 20:28             ` Mateusz Guzik
2016-07-31 18:45               ` Eric W. Biederman
2016-07-31 18:45               ` Eric W. Biederman
2016-08-22 15:40                 ` Richard Guy Briggs
2016-07-31 22:43             ` Cyrill Gorcunov
2016-07-31 22:49               ` Andy Lutomirski
2016-08-01  9:04             ` Cyrill Gorcunov
2016-08-10 10:48             ` Stanislav Kinsburskiy
2016-07-26 10:21     ` Stanislav Kinsburskiy

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=20160713101504.GB6569@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bsegall@google.com \
    --cc=ebiederm@xmission.com \
    --cc=gorcunov@openvz.org \
    --cc=john.stultz@linaro.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=matthltc@us.ibm.com \
    --cc=mguzik@redhat.com \
    --cc=mhocko@suse.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=skinsbursky@virtuozzo.com \
    --cc=vbabka@suse.cz \
    --cc=xemul@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.