Revision 5ccf92037c7c6e6f28175fd245284923f939259f authored by Tyler Hicks on 24 May 2011, 07:16:51 UTC, committed by Tyler Hicks on 29 May 2011, 17:51:17 UTC
The eCryptfs inode get, initialization, and dentry interposition code has two separate paths. One is for when dentry interposition is needed after doing things like a mkdir in the lower filesystem and the other is needed after a lookup. Unlocking new inodes and doing a d_add() needs to happen at different times, depending on which type of dentry interposing is being done. This patch cleans up the inode get and initialization code paths and splits them up so that the locking and d_add() differences mentioned above can be handled appropriately in a later patch. Signed-off-by: Tyler Hicks <tyhicks@linux.vnet.ibm.com> Tested-by: David <david@unsolicited.net>
1 parent c4f7907
