[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20070917210216.284780@gmx.net>
Date: Mon, 17 Sep 2007 23:02:16 +0200
From: "Michael Kerrisk" <mtk-manpages@....net>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: corbet@....net, jengelh@...putergmbh.de, hch@....de,
stable@...nel.org, drepper@...hat.com,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
tglx@...utronix.de, rdunlap@...otime.net, vda.linux@...glemail.com,
davidel@...ilserver.org
Subject: Re: [PATCH] remove timerd() syscall number
> > 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
> _
Cough! Right then. I take it you'll apply one of those then?
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages ,
read the HOWTOHELP file and grep the source
files for 'FIXME'.
-
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