linux-kernel - Re: kernel BUG at fs/btrfs/delayed-inode.c:1466!

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 9 Mar 2012 15:54:06 +0100
From:	David Sterba <dave@...os.cz>
To:	Jacek Luczak <difrost.kernel@...il.com>
Cc:	dave@...os.cz, Liu Bo <liubo2009@...fujitsu.com>,
	linux-btrfs <linux-btrfs@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>, josef@...hat.com
Subject: Re: kernel BUG at fs/btrfs/delayed-inode.c:1466!

On Fri, Mar 09, 2012 at 03:33:24PM +0100, Jacek Luczak wrote:
> > Those two issues go inline. After a longer while of WARN_ON the BUG_ON
> > hit again.
> 
> One more observation. Host is running builds from CI system. After
> BUG_ON pop up all builds take 50% more time to complete.

After a BUG_ON the system is in an inconsistent state and will
misbehave.

> Also I see that current load average stall at value of 7 even if host
> is completely idle.

That's probably because some process is stuck in a D-state after the
crash.


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