| 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
| ||
|
Date: Fri, 25 Jun 2010 16:04:41 -0400 (EDT) From: Ulrich Drepper <drepper@...hat.com> To: Thomas Gleixner <tglx@...utronix.de> Cc: Darren Hart <dvhltc@...ibm.com>, Ingo Molnar <mingo@...e.hu>, Linus Torvalds <torvalds@...ux-foundation.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Andreas Schwab <schwab@...hat.com>, Danny Feng <dfeng@...hat.com>, Jakub Jelinek <jakub@...hat.com>, linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com> Subject: Re: Q: sys_futex() && timespec_valid() ----- "Thomas Gleixner" <tglx@...utronix.de> wrote: > tv->sec < 0 is definitely an invalid value for both CLOCK_REALTIME > and CLOCK_MONOTONIC. CLOCK_MONOTONIC is different but it's wrong for CLOCK_REALTIME. Why would it be invalid? Because times before Epoch will not be used? By that logic you would have to declare all values before Linus' first running kernel as invalid. None of this makes sense. The tv_sec in timespec is of type time_t and for absolute time values the same semantics as for naked time_t values applies. The absolute time is epoch + tv_sec + tv_nsec / 1000000000 If tv_sec is negative these are values before epoch. If there are other interfaces with absolute timeouts they certainly should be changed as well. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ -- 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