From patchwork Fri Feb 26 13:05:08 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: ext3: explicitly remove inode from orphan list after failed direct_io From: Dmitri Monakho X-Patchwork-Id: 46328 Message-Id: <1267189508-5273-1-git-send-email-dmonakhov@openvz.org> To: linux-ext4@vger.kernel.org Cc: jack@suse.cz, Dmitry Monakhov Date: Fri, 26 Feb 2010 16:05:08 +0300 Otherwise non empty orphan list will be triggered on umount. Signed-off-by: Dmitry Monakhov --- fs/ext3/inode.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) 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)