linux-kernel - Re: [BUG] 3.3.0-rcX: kjournald

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]

Date:	Tue, 21 Feb 2012 07:42:40 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Bob Tracy <rct@...rkin.frus.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [BUG] 3.3.0-rcX: kjournald

On Mon, Feb 20, 2012 at 11:41:59PM -0600, Bob Tracy wrote:
> I'm not sure if I caught a complete instance of this in "syslog", but
> here's what I've been seeing with 3.3.0-rc[1-3] kernels.  Shortly after
> booting multi-user, logging in, and attempting a package build, the
> "fun" starts: the following message scrolls repeatedly (possibly with
> different details) across the console.  To date, I've had to hit the
> reset switch to recover, which is why I'm not sure whether I caught a
> complete syslog entry.

Hmm..  I've taken a quick look at fs/jbd/commit.c, and I don't see
anything obvious.  Can you try compiling with LOCKDEP compiled and see
if you can reproduce it, so we can see what spin lock is being held?

Thanks,

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