linux-ext4 - Re: help about ext3 read-only issue on ext3(2.6.16.30)

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:	Thu, 6 Dec 2012 23:48:20 +0800
From:	qixuan wu <wuqixuan@...il.com>
To:	Tao Ma <tm@....ma>
Cc:	"Theodore Ts'o" <tytso@....edu>, Li Zefan <lizefan@...wei.com>,
	Eric Sandeen <sandeen@...hat.com>,
	Yafang Shao <laoar.shao@...il.com>,
	linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
	wuqixuan@...wei.com
Subject: Re: help about ext3 read-only issue on ext3(2.6.16.30)

Hi Tao,

On Thu, Dec 6, 2012 at 9:54 AM, Tao Ma <tm@....ma> wrote:
> On 12/05/2012 11:05 PM, Theodore Ts'o wrote:
>> On Wed, Dec 05, 2012 at 09:58:17PM +0800, Tao Ma wrote:
>>> Are you sure the disk is good? I just checked the code in e2fsprogs, it
>>> seems that it will not complain if rec_len = 0, and the dir iteration
>>> just aborts.
>>
>> Um, where are you seeing this?  It should be complaining that the
>> directory entry is corrupt if rec_len < 12.  I believe I see the
>> checks there, but I haven't tried creating some test file systems to
>> be sure.
> Oh, sorry my fault. Yes, I see a final com_err in the end of do_list_dir
> in debugfs. So we should complain about the dir corruption.

I have already also checked the raw binary of the dir block in the
disk and the data is correct. So disk no issue, only data in mem is
corrupted.

> Thanks
> Tao
--
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