linux-kernel - Re: [PATCH] remove timerd() syscall number

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070917134315.968c1902.akpm@linux-foundation.org>
Date:	Mon, 17 Sep 2007 13:43:15 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Michael Kerrisk <mtk-manpages@....net>
Cc:	davidel@...ilserver.org, vda.linux@...glemail.com,
	rdunlap@...otime.net, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	drepper@...hat.com, stable@...nel.org, hch@....de,
	jengelh@...putergmbh.de, corbet@....net
Subject: Re: [PATCH] remove timerd() syscall number

On Mon, 17 Sep 2007 18:58:58 +0200
Michael Kerrisk <mtk-manpages@....net> wrote:

> I hope I've done this right...  This patch, against 2.6.23-rc6,
> removes the timerfd() syscall (which in any case had a bug
> on its 2.6.22 release) from all architectures, so that we
> can have some breathing space to think about the API design.
> All of the existing timerfd() code is left intact.

I think a minimally-intrusive implementation would be

--- a/fs/timerfd.c~a
+++ a/fs/timerfd.c
@@ -159,6 +159,8 @@ asmlinkage long sys_timerfd(int ufd, int
 	struct inode *inode;
 	struct itimerspec ktmr;
 
+	return -ENOSYS;
+
 	if (copy_from_user(&ktmr, utmr, sizeof(ktmr)))
 		return -EFAULT;
 
_

or, better,

--- a/init/Kconfig~a
+++ a/init/Kconfig
@@ -491,6 +491,7 @@ config SIGNALFD
 
 config TIMERFD
 	bool "Enable timerfd() system call" if EMBEDDED
+	depends on BROKEN
 	select ANON_INODES
 	default y
 	help
_

-
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/