linux-ext4 - Re: kernel BUG at fs/ext4/extents.c:2738!

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:	Fri, 20 Feb 2009 14:30:13 -0500
From:	Theodore Tso <tytso@....edu>
To:	Andreas Friedrich Berendsen <afberendsen@...il.com>
Cc:	linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: kernel BUG at fs/ext4/extents.c:2738!

On Sat, Feb 21, 2009 at 07:48:32AM +1300, Andreas Friedrich Berendsen wrote:
> ...I haven't noticed  before, but before that message few more lines
> where recorded, which makes sense with the BUG line. Also, running
> fsck.ext4 on that filesystem I always got a Segment fault at an specific
> point, which it is impossible to fix. I'm in a process to remove files
> from that filesystem, as soon it finish I can run fsck again and send
> the result. Meanwhile, when removing files, rm stuck at a certain inode,
> which caused the first BUG message.

Have you tried running e2fsck?  It sounds like a filesystem corruption
is triggering a BUG() message, which is obviously a bug in and of
itself.  :-)

						- Ted

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html