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:	Tue, 22 Jan 2013 23:31:16 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Zheng Liu <gnehzuil.liu@...il.com>
Cc:	linux-ext4@...r.kernel.org, Jan kara <jack@...e.cz>,
	Zheng Liu <wenqing.lz@...bao.com>
Subject: Re: [PATCH 5/7 v2] ext4: track all extent status in extent status
 tree

On Fri, Jan 11, 2013 at 06:53:45PM +0800, Zheng Liu wrote:
> From: Zheng Liu <wenqing.lz@...bao.com>
> 

Please line-wrap the commit description to 72 columns.  (This way the
output of "git log" will look nice even on 80 column terminal windows)".

> After record phycisal block and status, extent status tree is able to track the

"By recording the physical block and status, ...."

> status of every extents.  When we call _map_blocks functions to lookup an extent
> or create a new written/unwritten/delayed extent, this extent will be inserted
> into extent status tree.
> 
> We don't load all extents from disk in alloc_inode() because it costs too much
> memory, and, when open/close a file very frequently, it will takes too much time

"...and if a file is opened and closed frequently"..."

> to load all extent information.  So currently when we create/lookup an extent,
> this extent will be inserted into extent status tree.  Hence, the status in
> extent status tree might be not completely.

"Hence, the extent status tree may not comprehensively contain all of
the extents found in the file."

						- 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ