linux-ext4 - Re: Mentor for a GSoC application wanted (Online ext2/3 filesystem checker)

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: <20080421144332.GA21028@one.firstfloor.org>
Date:	Mon, 21 Apr 2008 16:43:32 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Theodore Tso <tytso@....EDU>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Alexey Zaytsev <alexey.zaytsev@...il.com>,
	linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Rik van Riel <riel@...riel.com>
Subject: Re: Mentor for a GSoC application wanted (Online ext2/3 filesystem checker)

> snaphot was taken.  Even if it has been remounted read-only at this
> point, this gets really dicey.  Consider that with certain types of
> corruption, if the filesystem continues to get modified, the
> corruption can get worse.

I see, but perhaps you could do that on at least some common
type of corruptions and only give up in the extreme cases?

Mind you I don't have a good feeling what common and uncommon 
types are.

> 
> > Or perhaps just tell the kernel which objects is suspicious and
> > should be EIOed.
> 
> Yeah; you could do that, as long as it's not a guarantee that all of
> the objects which were suspicious were found.  It would also be

Ok to do the 100% job you probably need metadata checksums and always
validate on initial read.

-Andi

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