The patch titled
Subject: ocfs2: fix d_splice_alias() return code checking
has been added to the -mm tree. Its filename is
ocfs2-fix-d_splice_alias-return-code-checking.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/ocfs2-fix-d_splice_alias-return-code-checking.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/ocfs2-fix-d_splice_alias-return-code-checking.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Richard Weinberger <richard@xxxxxx>
Subject: ocfs2: fix d_splice_alias() return code checking
d_splice_alias() can return a valid dentry, NULL or an ERR_PTR. Currently
the code checks not for ERR_PTR and my oops in ocfs2_dentry_attach_lock().
Fix this by using IS_ERR_OR_NULL().
Signed-off-by: Richard Weinberger <richard@xxxxxx>
Cc: Mark Fasheh <mfasheh@xxxxxxxx>
Cc: Joel Becker <jlbec@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/ocfs2/namei.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/ocfs2/namei.c~ocfs2-fix-d_splice_alias-return-code-checking fs/ocfs2/namei.c
--- a/fs/ocfs2/namei.c~ocfs2-fix-d_splice_alias-return-code-checking
+++ a/fs/ocfs2/namei.c
@@ -158,7 +158,7 @@ bail_add:
* NOTE: This dentry already has ->d_op set from
* ocfs2_get_parent() and ocfs2_get_dentry()
*/
- if (ret)
+ if (!IS_ERR_OR_NULL(ret))
dentry = ret;
status = ocfs2_dentry_attach_lock(dentry, inode,
_
Patches currently in -mm which might be from richard@xxxxxx are
ocfs2-fix-d_splice_alias-return-code-checking.patch
linux-next.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
