The patch titled
Subject: ocfs2_direct_IO_write() misses ocfs2_is_overwrite() error code
has been added to the -mm tree. Its filename is
ocfs2_direct_io_write-misses-ocfs2_is_overwrite-error-code.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/ocfs2_direct_io_write-misses-ocfs2_is_overwrite-error-code.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/ocfs2_direct_io_write-misses-ocfs2_is_overwrite-error-code.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: "Norton.Zhu" <norton.zhu@xxxxxxxxxx>
Subject: ocfs2_direct_IO_write() misses ocfs2_is_overwrite() error code
If ocfs2_is_overwrite failed, ocfs2_direct_IO_write mays till return
success to the caller.
Signed-off-by: Norton.Zhu <norton.zhu@xxxxxxxxxx>
Cc: Mark Fasheh <mfasheh@xxxxxxx>
Cc: Joel Becker <jlbec@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/ocfs2/aops.c | 1 +
1 file changed, 1 insertion(+)
diff -puN fs/ocfs2/aops.c~ocfs2_direct_io_write-misses-ocfs2_is_overwrite-error-code fs/ocfs2/aops.c
--- a/fs/ocfs2/aops.c~ocfs2_direct_io_write-misses-ocfs2_is_overwrite-error-code
+++ a/fs/ocfs2/aops.c
@@ -864,6 +864,7 @@ static ssize_t ocfs2_direct_IO_write(str
is_overwrite = ocfs2_is_overwrite(osb, inode, offset);
if (is_overwrite < 0) {
mlog_errno(is_overwrite);
+ ret = is_overwrite;
ocfs2_inode_unlock(inode, 1);
goto clean_orphan;
}
_
Patches currently in -mm which might be from norton.zhu@xxxxxxxxxx are
ocfs2_direct_io_write-misses-ocfs2_is_overwrite-error-code.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
