linux-ext4 - Re: [PATCH 01/51] libext2fs: Read and write full size inodes

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

Message-ID: <20111219174631.GF8233@tux1.beaverton.ibm.com>
Date:	Mon, 19 Dec 2011 09:46:31 -0800
From:	"Darrick J. Wong" <djwong@...ibm.com>
To:	Andreas Dilger <adilger.kernel@...ger.ca>
Cc:	Theodore Tso <tytso@....edu>,
	Sunil Mushran <sunil.mushran@...cle.com>,
	Amir Goldstein <amir73il@...il.com>,
	Andi Kleen <andi@...stfloor.org>,
	Mingming Cao <cmm@...ibm.com>,
	Joel Becker <jlbec@...lplan.org>, linux-ext4@...r.kernel.org,
	Coly Li <colyli@...il.com>
Subject: Re: [PATCH 01/51] libext2fs: Read and write full size inodes

On Mon, Dec 19, 2011 at 10:36:14AM +0100, Andreas Dilger wrote:
> <html><body class="ApplePlainTextBody" style="word-wrap: break-word;
<html mail snip>
> </span>}<br></blockquote><br>Instead of having an icache that is allocating
> temporary buffers<br>to handle the inode size mismatch, and then copying the
> inode data<br>into the icache each time, it makes more sense to use the
> allocated<br>buffers for the icache directly.<br><br>Cheers,
> Andreas<br><br><br><br><br><br></body></html>

Ok, I guess we can go for the larger reorganization of the code.  I was trying
not to read stuff into the cache before it was verified, but as long as we take
care of the cache bookkeeping it's fine.

--D

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