mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: akpm@osdl.org
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, drepper@redhat.com, mingo@elte.hu,
	rusty@rustcorp.com.au, tglx@linutronix.de
Subject: [patch 1/1] schedule removal of FUTEX_FD
Date: Tue, 31 Oct 2006 15:09:48 -0800	[thread overview]
Message-ID: <200610312309.k9VN9mco015260@shell0.pdx.osdl.net> (raw)

From: Andrew Morton <akpm@osdl.org>

Apparently FUTEX_FD is unfixably racy and nothing uses it (or if it does, it
shouldn't).

Add a warning printk, give any remaining users six months to migrate off it.

Cc: Ulrich Drepper <drepper@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Andrew Morton <akpm@osdl.org>
---

 kernel/futex.c |    8 ++++++++
 1 files changed, 8 insertions(+)

diff -puN kernel/futex.c~schedule-removal-of-futex_fd kernel/futex.c
--- a/kernel/futex.c~schedule-removal-of-futex_fd
+++ a/kernel/futex.c
@@ -1507,6 +1507,14 @@ static int futex_fd(u32 __user *uaddr, i
 	struct futex_q *q;
 	struct file *filp;
 	int ret, err;
+	static int warn_count;
+
+	if (warn_count < 10) {
+		printk(KERN_WARNING "Process `%s' used FUTEX_FD, which "
+		    	"will be removed from the kernel in June 2007\n",
+			current->comm);
+		warn_count++;
+	}
 
 	ret = -EINVAL;
 	if (!valid_signal(signal))
_

             reply	other threads:[~2006-10-31 23:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 23:09 akpm [this message]
2006-10-31 23:27 ` Thomas Gleixner
2006-10-31 23:48 ` Alan Cox
2006-11-01  0:05   ` Thomas Gleixner
2006-11-01  0:09   ` Andrew Morton
2006-11-01  1:19 ` Rusty Russell
2006-11-01  1:23   ` Andrew Morton
2006-11-01  9:11     ` bert hubert
2006-11-01  9:18       ` Andrew Morton
2006-11-01 10:03         ` bert hubert
2006-11-01 10:19   ` Eric Dumazet

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=200610312309.k9VN9mco015260@shell0.pdx.osdl.net \
    --to=akpm@osdl.org \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®