linux-ext4 - Re: [PATCH 2/2] ext4: Rename uninitialized extents to unwritten

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: <20140412142840.GF13837@thunk.org>
Date:	Sat, 12 Apr 2014 10:28:41 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Lukas Czerner <lczerner@...hat.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 2/2] ext4: Rename uninitialized extents to unwritten

On Thu, Apr 10, 2014 at 07:14:23PM +0200, Lukas Czerner wrote:
> Currently in ext4 there is quite a mess when it comes to naming
> unwritten extents. Sometimes we call it uninitialized and sometimes we
> refer to it as unwritten.
> 
> The right name for the extent which has been allocated but does not
> contain any written data is _unwritten_. Other file systems are
> using this name consistently, even the buffer head state refers to it as
> unwritten. We need to fix this confusion in ext4.
> 
> This commit changes every reference to an uninitialized extent (meaning
> allocated but unwritten) to unwritten extent. This includes comments,
> function names and variable names. It even covers abbreviation of the
> word uninitialized (such as uninit) and some misspellings.
> 
> This commit does not change any of the code paths at all. This has been
> confirmed by comparing md5sums of the assembly code of each object file
> after all the function names were stripped from it.
> 
> Signed-off-by: Lukas Czerner <lczerner@...hat.com>

Thanks, queued.

						- 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