linux-ext4 - Re: [PATCH v3 0/3] Add XIP support to ext4

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Dec 2013 11:17:28 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Dave Chinner <david@...morbit.com>,
	Matthew Wilcox <matthew.r.wilcox@...el.com>,
	linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v3 0/3] Add XIP support to ext4

On Thu, Dec 19, 2013 at 08:20:49AM -0700, Matthew Wilcox wrote:
> We could have ext4_get_xip_mem() check buffer_unwritten(); if it's set,
> zero the blocks and call ext4_convert_unwritten_extents().  Would that
> work?

That would work, but we'd be doing a double write to each data block
--- first writing all zero's, and then later, writing the actual data.
So this would halve our write bandwidth, and double the write wear on
the device.

And of course, if we did this on the read path, we'd be unnecessarily
doing an extent conversion.

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