linux-kernel - Re: [Ecryptfs-devel] [PATCH] ecryptfs: some inode attrs, and a question

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: <11994.1232378730@jrobl>
Date:	Tue, 20 Jan 2009 00:25:30 +0900
From:	hooanon05@...oo.co.jp
To:	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>
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 


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?
If so, I can understand why ecryptfs_link() sets i_size.


J. R. Okajima
--
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/