linux-ext4 - Re: [PATCH 0/8 v3] ext4: extent status tree (step 1)

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: <20121119031725.GA24414@thunk.org>
Date:	Sun, 18 Nov 2012 22:17:25 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Zheng Liu <gnehzuil.liu@...il.com>
Cc:	linux-ext4@...r.kernel.org, jeff.liu@...cle.com, hughd@...gle.com,
	xiaoqiangnk@...il.com, achender@...ux.vnet.ibm.com,
	lczerner@...hat.com, Zheng Liu <wenqing.lz@...bao.com>
Subject: Re: [PATCH 0/8 v3] ext4: extent status tree (step 1)

On Fri, Oct 26, 2012 at 09:23:37PM +0800, Zheng Liu wrote:
> Hi all,
> 
> Here is the v3 of extent status tree.  In this version, the biggest change is
> the i_es_lock (a rwlock_t) instead of i_data_sem, which is introduced to protect
> extent status tree.  Moreover I improve the SEEK_DATA/SEEK_HOLE.  In previous
> version, the unwritten extent is as a data, and now it will lookup page cache to
> determine it as a data or a hole.  When it has some data at the given range, the
> unwritten extent will be as a data.  Otherwise, it will be as a hole.  Other
> changes contain some bug fixes.

I don't think I ack'ed this patch series earlier; my apologies.  In
any case (with the comment fixup we discussed earlier), It's currently
queued for the next merge window.

Regards,

						- 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