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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CADDYkjRK3h_e3GPDQMpVwSwn6aQ5MwA1FoF1wFV05=LytK3chg@mail.gmail.com>
Date:	Fri, 9 Mar 2012 15:33:24 +0100
From:	Jacek Luczak <difrost.kernel@...il.com>
To:	dave@...os.cz, Jacek Luczak <difrost.kernel@...il.com>,
	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!

2012/3/9 Jacek Luczak <difrost.kernel@...il.com>:
> 2012/3/9 David Sterba <dave@...os.cz>:
>> On Fri, Mar 09, 2012 at 12:08:12PM +0100, Jacek Luczak wrote:
>>> For this one I've created also a report [1].
>>> >
>>> > so there is probably other problem in reservations and it just blew up during
>>> > the unlink call.
>>>
>>> Could be as this came up after a longer time of throwing above WARN_ON.
>>>
>>> I'm now cloning the Linus tree. Lets see if both will pop up on there.
>>
>> The 3.3-rc6 should help in one case, with
>>
>> http://thread.gmane.org/gmane.comp.file-systems.btrfs/15268
>>
>> but I was able to reproduce the WARN_ON even with this patch, didn't get
>> to debugging it again yet.
>
> 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. Also I see
that current load average stall at value of 7 even if host is
completely idle.

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