| 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
| ||
|
Message-Id: <1232379004.5893.7.camel@norville.austin.ibm.com> Date: Mon, 19 Jan 2009 09:30:04 -0600 From: Dave Kleikamp <shaggy@...ux.vnet.ibm.com> To: hooanon05@...oo.co.jp Cc: Tyler Hicks <tyhicks@...ux.vnet.ibm.com>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-kernel@...r.kernel.org, ecryptfs-devel@...ts.launchpad.net Subject: Re: [Ecryptfs-devel] [PATCH] ecryptfs: some inode attrs, and a question On Tue, 2009-01-20 at 00:25 +0900, hooanon05@...oo.co.jp wrote: > Dave Kleikamp: > > > > For a regular file, the size of the upper inode is not the same as the > > > > size of the lower inode. The lower inode includes the header blocks > > > > which are not visible in the upper inode. So ecryptfs_interpose() will > > > > overwrite the correct upper inode size. > ::: > > It's restoring i_size to the correct value after ecryptfs_interpose > > updates it with the wrong value. > > Does "ecryptfs_interpose() will overwrite the correct upper inode size" > means ecryptfs_interpose() sets a wrong value? Yes. ecryptfs_interpose() will copy the lower inode's size to the upper inode. For an encrypted file, the lower inode will have a larger size, since the lower file is prefixed with a header. > If so, I can understand why ecryptfs_link() sets i_size. Shaggy -- David Kleikamp IBM Linux Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists