linux-kernel - Re: RFC: A revised timerfd API

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 18 Sep 2007 13:30:11 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Michael Kerrisk <mtk-manpages@....net>
Cc:	david@...deman.nu, davidel@...ilserver.org, drepper@...hat.com,
	geoff@...are.org.uk, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, hch@....de, corbet@....net,
	rdunlap@...otime.net, vda.linux@...glemail.com,
	torvalds@...ux-foundation.org, Lee.Schermerhorn@...com
Subject: Re: RFC: A revised timerfd API

On Tue, 2007-09-18 at 13:08 +0200, Michael Kerrisk wrote:
> > > it does make the API a little more clumsy.
> > 
> > Hmm, we might do something like:
> > 
> > 	timer_gettime(fd | POSIX_TIMER_FD, .....);
> > 
> > So the kernel looks up the fd in order to figure out the timer_id, which
> > needs to be referenced in filep->private_data anyway.
> 
> And you'd need similar for timer_settime() and, perhaps,
> timer_getoverrun().  But it seems slightly ugly, in the same way that
> my idea in option (d) of returning a file descriptor from
> timer_create() seems a slightly ugly.  (And can we guarantee that
> the [timerid] space is distinct from the [fd|POSIX_TIMER_FD] space?)

If we use the most significant bit for POSIX_TIMER_FD, we should be
fine.

	tglx


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