linux-kernel - Re: [Bug #14256] kernel BUG at fs/ext3/super.c:435

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19151.26501.727411.584056@pilspetsen.it.uu.se>
Date:	Fri, 9 Oct 2009 18:40:37 +0200
From:	Mikael Pettersson <mikpe@...uu.se>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #14256] kernel BUG at fs/ext3/super.c:435

Mikael Pettersson writes:
 > Rafael J. Wysocki writes:
 >  > On Sunday 04 October 2009, Mikael Pettersson wrote:
 >  > > Rafael J. Wysocki wrote:
 >  > > > The following bug entry is on the current list of known regressions
 >  > > > introduced between 2.6.30 and 2.6.31.  Please verify if it still should
 >  > > > be listed and let me know (either way).
 >  > > > 
 >  > > > 
 >  > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=3D14256
 >  > > > Subject		: kernel BUG at fs/ext3/super.c:435
 >  > > > Submitter	: Mikael Pettersson <mikpe@...uu.se>
 >  > > > Date		: 2009-09-21 7:29 (11 days old)
 >  > > > References	: http://marc.info/?l=3Dlinux-kernel&m=3D125351816109264&w=3D4
 >  > > 
 >  > > The exact same bug (same cause, same symptom) just hit me again in 2.6.32-rc1.
 >  > 
 >  > Thanks for the update.
 >  > 
 >  > Could you check the current Linus' tree, please?  There are some known
 >  > regression fixes in there.
 > 
 > I tried simplified versions of the bug trigger on two machines
 > running 2.6.32-rc1-git6, and neither triggered the kernel bug.
 > 
 > The original recipe involved doing a glibc rebuild, run its test
 > suite, install it, and reboot. Today however machine 1 was already
 > doing a rebuild so after the rebuild it did a reboot into the new
 > kernel before the install. The second machine booted the new kernel
 > directly to install the binary packages from the first machine.
 > 
 > I'll re-run the full bug trigger recipe on a third machine later next
 > week (it must rebuild glibc itself anyway due to arch differences).

Not fixed in 2.6.32-rc3. A glibc rebuild + install triggered the
exact same bug on the third machine.

/Mikael
--
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/