From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
LKML <linux-kernel@vger.kernel.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Oleg Nesterov <oleg@redhat.com>,
Pavel Emelyanov <xemul@parallels.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>
Subject: Re: [PATCH] fcntl: Add F_GETOWNER_UIDS option v3
Date: Wed, 6 Jun 2012 10:22:50 +0400 [thread overview]
Message-ID: <20120606062250.GA1934@moon> (raw)
In-Reply-To: <20120605154743.53d494e6.akpm@linux-foundation.org>
On Tue, Jun 05, 2012 at 03:47:43PM -0700, Andrew Morton wrote:
> >
> > This option is valid iif CONFIG_CHECKPOINT_RESTORE
> > is turned on, otherwise returning -EINVAL.
>
> um, OK.
>
> But we still have
>
> c-r-prctl-add-ability-to-set-new-mm_struct-exe_file-update-after-mm-num_exe_file_vmas-removal.patch
> c-r-prctl-add-ability-to-set-new-mm_struct-exe_file-add-minimal-address-test-to-pr_set_mm.patch
> c-r-prctl-add-ability-to-get-clear_tid_address.patch
> c-r-prctl-drop-vma-flags-test-on-pr_set_mm_-stack-data-assignment.patch
>
> floating about unmerged due to various unresolved issues. Can we
> please get all that stuff nailed down before working on new things?
Hmm, Andrew, I must admit I don't understand which unresolved issues
here with the rest of prctl SET_MM code. Could you please clarify?
Do they not apply on current linux-next, or something like that?
Cyrill
prev parent reply other threads:[~2012-06-06 6:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 8:25 [PATCH] fcntl: Add F_GETOWNER_UIDS option v3 Cyrill Gorcunov
2012-06-05 16:14 ` Eric W. Biederman
2012-06-05 16:24 ` Cyrill Gorcunov
2012-06-05 16:40 ` Eric W. Biederman
2012-06-05 22:47 ` Andrew Morton
2012-06-05 23:09 ` Eric W. Biederman
2012-06-06 6:22 ` Cyrill Gorcunov [this message]
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=20120606062250.GA1934@moon \
--to=gorcunov@openvz.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=serge@hallyn.com \
--cc=xemul@parallels.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.