linux-ext4 - Re: [PATCH 4/5] fix transaction issues for ext4_fallocate and ext_zero

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:	Mon, 25 Aug 2014 21:30:55 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>
Cc:	linux-ext4@...r.kernel.org, lczerner@...hat.com
Subject: Re: [PATCH 4/5] fix transaction issues for ext4_fallocate and
 ext_zero_range

On Fri, Aug 22, 2014 at 03:32:26PM +0400, Dmitry Monakhov wrote:
> After commit f282ac19d86f we use different transactions for preallocation
> and i_disksize update which result in complain from fsck after power-failure.
> spotted by generic/019. IMHO this is regression because fs becomes inconsistent,
> even more 'e2fsck -p' will no longer works (which drives admins go crazy)
> Same transaction requirement applies ctime,mtime updates
> 
> testcase: xfstest generic/019
> 
> Signed-off-by: Dmitry Monakhov <dmonakhov@...nvz.org>

Applied, thanks.

					- 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