The patch titled ecryptfs: fix OOPs after umount has been removed from the -mm tree. Its filename was ecryptfs-fix-oops-after-umount.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: ecryptfs: fix OOPs after umount From: Christian Ehrhardt <lk@xxxxxxx> Remove a d_drop in ecryptfs that is bogus IMHO. This d_drop unhashes a perfectly valid and reachable dentry in the lower FS. The patch fixes this perfectly reproducible kernel oops: https://bugzilla.kernel.org/show_bug.cgi?id=10907 It and may or may not be related to this ecryptfs bug: https://bugs.launchpad.net/ecryptfs/+bug/363734 At least the BUG_ON is on a dentry that should not be unhashed but is. regards Christian Signed-off-by: Christian Ehrhardt <lk@xxxxxxx> Cc: "Rafael J. Wysocki" <rjw@xxxxxxx> Cc: Eric Paris <eparis@xxxxxxxxxx> Cc: Tyler Hicks <tyhicks@xxxxxxxxxxxxxxxxxx> Cc: Dustin Kirkland <kirkland@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/ecryptfs/super.c | 1 - 1 file changed, 1 deletion(-) diff -puN fs/ecryptfs/super.c~ecryptfs-fix-oops-after-umount fs/ecryptfs/super.c --- a/fs/ecryptfs/super.c~ecryptfs-fix-oops-after-umount +++ a/fs/ecryptfs/super.c @@ -85,7 +85,6 @@ static void ecryptfs_destroy_inode(struc if (lower_dentry->d_inode) { fput(inode_info->lower_file); inode_info->lower_file = NULL; - d_drop(lower_dentry); } } ecryptfs_destroy_crypt_stat(&inode_info->crypt_stat); _ Patches currently in -mm which might be from lk@xxxxxxx are -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html