[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120606062250.GA1934@moon>
Date: Wed, 6 Jun 2012 10:22:50 +0400
From: Cyrill Gorcunov <gorcunov@...nvz.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
LKML <linux-kernel@...r.kernel.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Oleg Nesterov <oleg@...hat.com>,
Pavel Emelyanov <xemul@...allels.com>,
Konstantin Khlebnikov <khlebnikov@...nvz.org>
Subject: Re: [PATCH] fcntl: Add F_GETOWNER_UIDS option v3
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists