stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Richard Weinberger <richard@nod.at>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	paul.gortmaker@windriver.com, davej@redhat.com,
	keescook@chromium.org, stable@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: + futex-avoid-kernel-taint-caused-by-get_robust_list.patch added to -mm tree
Date: Mon, 18 Feb 2013 09:55:10 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1302180949240.22263@ionos> (raw)
In-Reply-To: <20130216070240.GA20312@moon>

On Sat, 16 Feb 2013, Cyrill Gorcunov wrote:

> On Fri, Feb 15, 2013 at 11:44:44PM +0100, Richard Weinberger wrote:
> > > The ability to deprecate this code has been called into question[1],
> > > but if that remains to be finalized, then making this change in the
> > > interim seems to make sense.
> > 
> > Do we really want to remove this system call in 2013?
> > Note, Documentation/feature-removal-schedule.txt is gone...
> > 
> > CRIU folks, I guess you still need the call?
> > Or have you found an alternative way to get the robost list?
> 
> Yes, we need this call and we use it.
> 
> > As stated in [0], I'd simply revert commit ec0c4274 ("futex: Mark
> > get_robust_list as deprecated")
> 
> Thanks!

I take the revert via tip and queue it for 3.9

Thanks,

	tglx
 

      reply	other threads:[~2013-02-18  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130215222653.B8B115A41F0@corp2gmr1-2.hot.corp.google.com>
2013-02-15 22:44 ` + futex-avoid-kernel-taint-caused-by-get_robust_list.patch added to -mm tree Richard Weinberger
2013-02-15 22:58   ` Andrew Morton
2013-02-16  7:02   ` Cyrill Gorcunov
2013-02-18  8:55     ` Thomas Gleixner [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=alpine.LFD.2.02.1302180949240.22263@ionos \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=gorcunov@openvz.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.org \
    /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).