linux-ext4 - Re: [PATCH v1 0/5] ext4: Shut down block groups when damage is detected

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: <x49txjdbd21.fsf@segfault.boston.devel.redhat.com>
Date:	Mon, 29 Jul 2013 11:28:38 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Zheng Liu <gnehzuil.liu@...il.com>
Cc:	"Darrick J. Wong" <darrick.wong@...cle.com>,
	"Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH v1 0/5] ext4: Shut down block groups when damage is detected

Zheng Liu <gnehzuil.liu@...il.com> writes:

> My idea is to let file system can ignore the currurted block.  Namely,
> when we meet a currupted block, we will track it as bad block in bad
> block inode and find another block to save data.  This currupted block
> will never be used.  The first step in my mind is to detect a currpted
> block and mark it as bad block.  After reading the thread and Darrick's
> original patch, I think Darrick's patch is a good start.

I think it's important to call out the exact failure scenario you're
trying to address.  For hard disks, if you get a read error, it can
typically be recovered by re-writing the block.  I imagine this is what
fsck would be doing for metadata repair.  So, I'm not at all sure why
you'd want to track bad blocks in the file system itself.  Could you
elaborate, please?

Cheers,
Jeff
--
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