linux-kernel - Re: kernel BUG at fs/btrfs-stable/extent-tree.c:2111!

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] [day] [month] [year] [list]

Message-ID: <20080903150304.GA31775@unused.rdu.redhat.com>
Date:	Wed, 3 Sep 2008 11:03:04 -0400
From:	Josef Bacik <jbacik@...hat.com>
To:	Ryan Hope <rmh3093@...il.com>
Cc:	Toei Rei <toei.rei@...rgazer.at>,
	linux-btrfs <linux-btrfs@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: kernel BUG at fs/btrfs-stable/extent-tree.c:2111!

On Wed, Sep 03, 2008 at 11:03:55AM -0400, Ryan Hope wrote:
> I dont think that is the case, the compressed reiser4 partition only
> had 1.6gig of data, uncompressed on my ext3 partition is about 2.2
> gig. The btrfs image I made was 3gig so I dont think it ran out of
> space.
>

Yeah you ran out of space.  There are a few weird things about the allocator, so
once you start getting to about 60% full you run the chance of not being able to
allocate more chunks, and therefore run the risk of not being able to allocate
space for something and then trip one of the millions of BUG()'s that are
sitting around to trap those cases.  Hopefully 0.16 will be a little less pissy
about this.

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