linux-ext4 - Re: Metadata reservation for unwritten extent conversion

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: <20130313172521.GC5604@thunk.org>
Date:	Wed, 13 Mar 2013 13:25:21 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Lukáš Czerner <lczerner@...hat.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Metadata reservation for unwritten extent conversion

On Wed, Mar 13, 2013 at 05:09:51PM +0100, Lukáš Czerner wrote:
> 
> Well, we can not actually revert that patch because it introduces
> da_reserve_metadata() which is used elsewhere in the commit:
> 
> ext4: reserve metadata block for every delayed write
> 
> I can resend the patch which uses da_reserve_metadata() so you can use
> it instead the old version

That sounds like the best thing to do.  I assume you will be simply
taking the da_reserve_metadata() function introduced in the
to-be-dropped commit:

> ext4: Reserve metadata if writing into uninitialized

... and moving it into the "reserve metadata block for every delayed
write" patch?

					- 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