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: Mon, 10 Jun 2013 16:12:09 +0200 (CEST) From: Thomas Gleixner <tglx@...utronix.de> To: Chen Gang <gang.chen@...anux.com> cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] kernel: timer: looping issue, need reset variable 'found' On Sun, 9 Jun 2013, Chen Gang wrote: > > According to __internal_add_timer(), in _next_timer_interrupt(), when > 'tv1.vec' find one, but need 'cascade bucket(s)', we still need find > each slot of 'tv*.vec'. No, we do not. We only need to scan the first cascade array after the enqueued timer. If there is nothing in tv2 which might come before the found timer, then any timer in tv3 will be later than the one we found in the primary wheel. > So need reset variable 'found', so can fully scan ''do {...} while()'' > for 'tv*.vec'. And thereby lose the information, that we already found a timer in the scan of the primary array. Thanks, 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/
Powered by blists - more mailing lists