linux-kernel - Re: 2.6.36: kernel panic in cascade (Fatal exception in interrupt)

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: <20101113233353.GB18658@thunk.org>
Date:	Sat, 13 Nov 2010 18:33:53 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Thomas Meyer <thomas@...3r.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-ext4@...r.kernel.org
Subject: Re: 2.6.36: kernel panic in cascade (Fatal exception in interrupt)

On Wed, Nov 10, 2010 at 08:43:04PM +0100, Thomas Meyer wrote:
> > 
> > I leave it to the ext4 experts to solve it for real :)
> > 
> 
> I just booted into 2.6.37-rc1-00166-g814ce25 and I don't see above bug
> in this kernel. So it seems as this bug got fixed in between 2.6.36 and
> 2.6.37-rc1+

Yes, this was fixed in 2.6.37-rc1 in commit: a1c6c5698d53 (ext4: fix
NULL pointer dereference in print_daily_error_info()).  I'll put it on
my list of things to be backported to 2.6.36.

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