linux-kernel - Re: kernel BUG at fs/ext3/namei.c:383

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: <e9e943910802280821q7fa5d0e2ya92023d46bcdb392@mail.gmail.com>
Date:	Thu, 28 Feb 2008 16:21:29 +0000
From:	"Duane Griffin" <duaneg@...da.com>
To:	"Abel Bernabeu" <abel.bernabeu@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: kernel BUG at fs/ext3/namei.c:383

On 28/02/2008, Abel Bernabeu <abel.bernabeu@...il.com> wrote:
> My kernel says that has a bug.
>
>  I attach two logs:
>
>  1) The output of dmesg.
>  2) The output printed in my console.
>
>  In defense of Linux I have to admit that I previously used the EXT3
>  filesystem that kernel was trying to access with Windows (by means of
>  an EXT2 driver from http://www.fs-driver.org/).

This is fixed in recent kernels (commit
3d82abae9523c33d4a16fdfdfd2bdde316d7b56a, to be precise). The windows
driver is corrupting the filesystem but ext3 shouldn't BUG and if you
update to a recent kernel it won't. If you can't update then you
should e2fsck the filesystem after using the windows driver. That
should fix up the corruption.

Also, for future reference, LKML folks generally don't like
attachments, so if possible just include logs or other info inline
next time.

>  Yours, Abel.

Cheers,
Duane.

-- 
"I never could learn to drink that blood and call it wine" - Bob Dylan
--
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/