From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Cyrill Gorcunov <gorcunov@openvz.org>,
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: Tue, 05 Jun 2012 16:09:09 -0700 [thread overview]
Message-ID: <877gvl4aqy.fsf@xmission.com> (raw)
In-Reply-To: <20120605154743.53d494e6.akpm@linux-foundation.org> (Andrew Morton's message of "Tue, 5 Jun 2012 15:47:43 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> 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?
Andrew I understand the frustration but in fairness this patch is just
as old as the patches you are talking about. Cyrill just finished
resolving the unresolved isssues with this one, aka a conflict with
user namespace support.
Now I do agree that we need to finish the rest of these things.
Eric
next prev parent reply other threads:[~2012-06-05 23:09 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 [this message]
2012-06-06 6:22 ` Cyrill Gorcunov
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=877gvl4aqy.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=gorcunov@openvz.org \
--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.