| 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: Sun, 17 Aug 2008 23:03:23 -0400 From: Shane <gnome42@...il.com> To: linux-kernel@...r.kernel.org Subject: WTF does -rc mean? was [PATCH] x86, tsc: fix section mismatch warning Adrian Bunk wrote .... |On Sun, Aug 10, 2008 at 10:07:31PM -0700, H. Peter Anvin wrote: |> Thanks! |> |> I have pulled these four patches into tip:x86/cleanups. | |Section fixes are not cleanups but bugfixes. | |E.g. this patch by Marcin fixes the following 2.6.27 regression |(that was found 4 days after you applied his patch): |http://bugzilla.kernel.org/show_bug.cgi?id=11330 | |Can you make sure that Marcin's bugfixes makes it into 2.6.27? | |> -hpa | |TIA |Adrian ------------------------------------------------------------------------------------------------------ This bug was causing my system to hang during boot at "Setting the system Clock". This was completely stopping me from testing the -rc3 kernel. I only tried this patch on a hunch (tsc == clock :), I'm on intel hardware. [ To: Adrian Bunk, Mark Lord (and other people with similar attitudes/ethics) thanks for fixing and tracking everyone elses bugs for us lusers. And the following hopefully scorching flame is not meant for you guys. ] This is the third** -rc cycle where I have composed what is meant to be a scorching email to the kernel list about the mind blowing decline in -rc kernel developer attitude. I didn't send the other two but I just spent another two flippin' hours booting and fsck'in. And I am very cranky (to put it politely) because the bleep'n problem is known and the fix has been available for at least 7 days!! I of course understand that there will be bugs in the -rc kernels, that is why I bother putting the time and energy into testing them. It is mainly the lackadaisical attitude about getting the fixes in that is a mind blower. I am a (fairly long time) tester/luser of the kernel. I do it for fun and to learn. It isn't fun anymore. ** A couple examples of what I'm talking about: http://www.gossamer-threads.com/lists/linux/kernel/852762#852762 http://www.gossamer-threads.com/lists/linux/kernel/853094#853094 This one is my least favourite. That r8169 bug required me to unplug my box overnight just to get back on the network. I foolishly thought that a bug like that on such a popular piece of hardware would not be allowed to persist in mainline for long, so I foolishly updated my kernel a few times (waiting days in between) and my box was basically bricked overnight each time!! :(( The maintainer's attitude makes me want to chisel that chip right off my board. Thanks again to Mark Lord! http://www.gossamer-threads.com/lists/linux/kernel/841017#841017 Andrew was my hero on this one. Thanks Andrew! http://www.gossamer-threads.com/lists/linux/kernel/852734#852734 ( I doubt I have anything else useful to say about this so I likely won't be posting again to this thread ) Shane -- 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