ext3: explicitly remove inode from orphan list after failed direct_io

Submitted by Dmitri Monakho on Feb. 26, 2010, 1:05 p.m.

Details

Message ID 1267189508-5273-1-git-send-email-dmonakhov@openvz.org
State Not Applicable, archived
Headers show

Commit Message

Dmitri Monakho Feb. 26, 2010, 1:05 p.m.
Otherwise non empty orphan list will be triggered on umount.

Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
---
 fs/ext3/inode.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

Patch hide | download patch | download mbox

diff --git a/fs/ext3/inode.c b/fs/ext3/inode.c
index cf0e3aa..2522106 100644
--- a/fs/ext3/inode.c
+++ b/fs/ext3/inode.c
@@ -1818,6 +1818,9 @@  retry:
 			 * but cannot extend i_size. Bail out and pretend
 			 * the write failed... */
 			ret = PTR_ERR(handle);
+			if (inode->i_nlink)
+				ext3_orphan_del(NULL, inode);
+
 			goto out;
 		}
 		if (inode->i_nlink)