The patch titled ufs: remove incorrect unlock_kernel from failure path in ufs_symlink() has been added to the -mm tree. Its filename is ufs-remove-incorrect-unlock_kernel-from-failure-path-in-ufs_symlink.patch See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: ufs: remove incorrect unlock_kernel from failure path in ufs_symlink() From: Josh Triplett <josht@xxxxxxxxxx> ufs_symlink, in one of its error paths, calls unlock_kernel without ever having called lock_kernel(); fix this by creating and jumping to a new label out_notlocked rather than the out label used after calling lock_kernel(). Signed-off-by: Josh Triplett <josh@xxxxxxxxxxxxxxx> Cc: Evgeniy Dushistov <dushistov@xxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- fs/ufs/namei.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff -puN fs/ufs/namei.c~ufs-remove-incorrect-unlock_kernel-from-failure-path-in-ufs_symlink fs/ufs/namei.c --- a/fs/ufs/namei.c~ufs-remove-incorrect-unlock_kernel-from-failure-path-in-ufs_symlink +++ a/fs/ufs/namei.c @@ -129,7 +129,7 @@ static int ufs_symlink (struct inode * d struct inode * inode; if (l > sb->s_blocksize) - goto out; + goto out_notlocked; lock_kernel(); inode = ufs_new_inode(dir, S_IFLNK | S_IRWXUGO); @@ -155,6 +155,7 @@ static int ufs_symlink (struct inode * d err = ufs_add_nondir(dentry, inode); out: unlock_kernel(); +out_notlocked: return err; out_fail: _ Patches currently in -mm which might be from josht@xxxxxxxxxx are release-dentry_lock-in-an-error-path-of-nfs_path.patch remove-incorrect-unlock_kernel-from-allocation.patch remove-incorrect-unlock_kernel-from-failure-path-in.patch add-entry-for-efs-filesystem-to-maintainers-as-orphan.patch ufs-remove-incorrect-unlock_kernel-from-failure-path-in-ufs_symlink.patch - 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