| 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: Tue, 29 Jan 2013 22:32:53 +0100 From: Sebastian Andrzej Siewior <bigeasy@...utronix.de> To: jlmales@...il.com CC: linux-kernel@...r.kernel.org Subject: Re: Kernel Failure - 3.4.24 On 01/28/2013 08:57 PM, John L. Males wrote: > I was not suggesting you are responsible for the bug at all. On Okay then :) > I have no custom patches to the kernel. okay. > I looked at the RedHat bug 468794. The bug seems to indicate it > was never fixed. The bug was reported against > 2.6.27.4-47.rc3.fc10.i686 #1 on 2008-10-27 21:34:04 EDT and was > closed 2009-12-18 01:40:33 EST. The differences are a bug of at > least 5 years ago and a 2.6 kernel verses 5 years later and current > at time stable kernel 3.4.24 from kernel.org with no patches I > applied when this kernel failure I encountered occurred. If this > is the same bug then there is a bug that may have been about for a > while or perhaps a regression. The fact is the RedHat bug 468794 > was never fixed. Lets see. According to the backtrace it seems that the kernel was not able to write the buffer back to disk. The RH bug says that someone unplugged the device without an unmount of the disk. My question are: - what were you doing by the time this happened? - can you reproduce it (reliably)? - Is this *new* meaning is there a kernel where did not happen? Sebastian -- 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