linux-ext4 - Re: [PATCH 3/6] ext4: Do not clear EOFBLOCKS

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: <20111025081834.GB31921@thunk.org>
Date:	Tue, 25 Oct 2011 04:18:34 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>
Cc:	linux-ext4@...r.kernel.org, achender@...ux.vnet.ibm.com
Subject: Re: [PATCH 3/6] ext4: Do not clear EOFBLOCKS_FL too soon

On Fri, Oct 21, 2011 at 01:08:56AM +0400, Dmitry Monakhov wrote:
> ext4_ext_insert_extent() may fail due to number of reasons (ENOSPC)
> so let's update eof flag only after extent was successfully inserted.
> 
> Signed-off-by: Dmitry Monakhov <dmonakhov@...nvz.org>

The problem with this patch is that if the check_eofblocks_fl() fails,
the patch jumps to out: and doesn't undo the block allocation and
extent tree manipulation.

I suspect a better way of solving this problem is to keep the existing
order, but to save the state of eofblocks flag, and if
ext4_ext_insert_extent() fails, to restore the state of the eofblocks
flag before jumping to the exit routine.

					- 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