linux-ext4 - [PATCH 0/2] ext4: cache uninitialized extents

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-next>] [day] [month] [year] [list]

Message-Id: <1321240026-844-1-git-send-email-xiaoqiangnk@gmail.com>
Date:	Mon, 14 Nov 2011 11:07:04 +0800
From:	Yongqiang Yang <xiaoqiangnk@...il.com>
To:	linux-ext4@...r.kernel.org
Cc:	tytso@....edu
Subject: [PATCH 0/2] ext4: cache uninitialized extents

Hi,

   Currently, ext4 caches holes and initialized extents in
ext4_ext_map_blocks() while it does not cache uninitialized
extents.  I noticed ext4 can cache uninitialized extents with
minor changes. ec_start is 0 means that the cached extent is
a hole, initialized extents' length is limited. So if ec_start
is not 0 and the cached extent's length is larger than EXT_MAX_LENGTH,
then the cached extent is uninitialized.

  This patch series tries to let ext4 cache uninitialized extents
with minor changes.

  The patches pass xfstests 1-268.  The xfstessts 268 and 272 meet
a bug in ext4 related to changing journal mode in flight.  I will
fix the bug in later patches.

  Any feedbacks and comments are welcome.

Yongqiang.

--
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