| 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: <1186954962.8166.19.camel@localhost> Date: Sun, 12 Aug 2007 16:42:42 -0500 From: Chris Holvenstot <cholvenstot@...cast.net> To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Kernel 2.6.23-rc2 git4 & git5 This morning I reported an issue which cause a failure of the 2.6.23-rc2-git4 kernel to boot on my system. The contents of my post may be viewed here: http://www.ussg.iu.edu/hypermail/linux/kernel/0708.1/1959.html After 3 separate builds from "virgin sources" I still had the boot failure with the git4 level kernel. This afternoon I picked up the git5 patch and it comes up and appears to run without problem. Same base system. Same hardware. Same build process. So even though I have only been building and running "pre-release" kernels for a short time I feel confident in saying that something was not kosher with the git4 patch - at least when it came to my system. (system configuration data is in the original post) I would not normally burn the valuable time of others with a rhetorical post but I looked at the changes out into the git5 patch and did not spot anything that looked like it would have resolved the issue I was having and I hate not being able to correlate a cause and effect here. Any clues, or did I just get lucky with this one? - 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