linux-kernel - Re: [patch 1/2] timerfd add flags check

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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0902081836540.18839@alien.or.mcafeemobile.com>
Date:	Sun, 8 Feb 2009 18:38:45 -0800 (PST)
From:	Davide Libenzi <davidel@...ilserver.org>
To:	mtk.manpages@...il.com
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg KH <greg@...ah.com>, Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [patch 1/2] timerfd add flags check

On Mon, 9 Feb 2009, Michael Kerrisk wrote:

> On Mon, Feb 9, 2009 at 12:23 PM, Davide Libenzi <davidel@...ilserver.org> wrote:
> > Like Michael requested, this patch adds a missing check for valid flags in
> > timerfd_settime(), and make it return EINVAL in case some extra bits are
> > set. If this is or not a -stable thing, it Greg decision.
> > Should be queued by Andrew for .30, unless -stable and Linus decide to
> > get it before, like Michael suggested.
> 
> When these two patches are applied against .29-rc3:
> 
> $ make
> [...]
>   CC      fs/timerfd.o
> fs/timerfd.c: In function 'sys_timerfd_create':
> fs/timerfd.c:190: error: implicit declaration of function 'invalid_clockid'
> make[1]: *** [fs/timerfd.o] Error 1
> make: *** [fs] Error 2

Yeah, I missed the posix-timers.h inclusion in timerfd.c, when I split the 
first patch into two separate ones. Will re-send tomorrow.


- Davide


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