| 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
| ||
|
Message-Id: <20070525091743.5fb569a8.akpm@linux-foundation.org> Date: Fri, 25 May 2007 09:17:43 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Andi Kleen <andi@...stfloor.org> Cc: Ingo Molnar <mingo@...e.hu>, Satyam Sharma <satyam.sharma@...il.com>, linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...ux-foundation.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl> Subject: Re: [patch] sched_clock(): cleanups, #2 On Fri, 25 May 2007 14:15:40 +0200 Andi Kleen <andi@...stfloor.org> wrote: > -Andi (who hopes this thread will end soon now and we can all go > back to more important issues) fyi, the thread has been damn useful for me. If Ingo hadn't spotted that preempt_count() imbalance then there's a decent chance that I'd have been the first to hit it. Time to bisect 1,000 patches: maybe an hour, if I choose the x86 tree as the first pivot point, which is likely. Or I wouldn't have hit it, in which case a tester hits it, and someone (guess who) gets to enter into an intercontinental head-scratching session trying to work out who broke it this time, consuming the tester's time too. Plus we have a wrecked -mm and other people's code doesn't get as well-tested as it might. All for one silly little mistake. So. More care, please. - 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