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: <20090423041914.GA2723@mit.edu>
Date:	Thu, 23 Apr 2009 00:19:14 -0400
From:	Theodore Tso <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4: Make the extent validity check more paranoid

On Wed, Apr 22, 2009 at 09:04:30PM -0500, Eric Sandeen wrote:
> Theodore Ts'o wrote:
> > Instead of just checking that the extent block number is greater or
> > equal than s_first_data_block, make sure it it is not pointing into
> > the block group descriptors, since that is clearly wrong.  This helps
> > prevent filesystem from getting very badly corrupted in case an extent
> > block is corrupted.
> > 
> > Signed-off-by: "Theodore Ts'o" <tytso@....edu>
> 
> Good idea.  Maybe we can get our friends with the corrupted fs to run
> with these validation patches... I can get this into rawhide at least.

Yeah, unfortunately this patch requires some other patches that went
in during the 2.6.30 merge window, so some extra back-porting would be
needed for our friends running a 2.6.29.1 Fedora kernel.

I'm still trying figure out what's the best way to add the right kind
of checking for 2.6.29 based kernels.  Looking at the dump files which
Kevin Shanahan, it doesn't look like they are coming from interior
nodes of extent trees.  Some kind of kludge patch into the block
device layer might be the most fool-proof way to do things.

       	     	      	       		  - 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ