ocfs2: need rollback when journal_access failed in ocfs2_orphan_add()
PATCH v2 1/1 ocfs2: need rollback when journal_access failed in ocfs2_orphan_add()
While adding a file into orphan dir in ocfs2_orphan_add(), it calls __ocfs2_add_entry() before ocfs2_journal_access_di(). If ocfs2_journal_access_di() failed, the file is added into orphan dir, and orphan dir dinode updated, but file dinode has not been updated.
Accordingly, the data is not consistent between file dinode and orphan dir.
So, need to call ocfs2_journal_access_di() before __ocfs2_add_entry(), and if ocfs2_journal_access_di() failed, orphan_fe and orphan_dir_inode->i_nlink need rollback.
--- fs/ocfs2/namei.c | 39 +++++++++++++++++++++++---------------- 1 file changed, 23 insertions(+), 16 deletions(-)
fs/ocfs2/namei.c +23 -16
@@ -2012,6 +2012,21 @@ static int ocfs2_orphan_add(struct ocfs2_super *osb, goto leave; } +/* +* We're going to journal the change of i_flags and i_orphaned_slot. +* It's safe anyway, though some callers may duplicate the journaling. +* Journaling within the func just make the logic look more +* straightforward. +*/ + status =ocfs2_journal_access_di (handle, +INODE_CACHE (inode), + fe_bh, +OCFS2_JOURNAL_ACCESS_WRITE ); +if (status <0 ) { +mlog_errno (status); + goto leave; + } +/* we're a cluster, and nlink can change on disk from * underneath us... */ orphan_fe = (struct ocfs2_dinode *) orphan_dir_bh->b_data;
@@ -2026,22 +2041,7 @@ static int ocfs2_orphan_add(struct ocfs2_super *osb, orphan_dir_bh, lookup);if (status <0 ) {mlog_errno (status); - goto leave; - } - -/* -* We're going to journal the change of i_flags and i_orphaned_slot. -* It's safe anyway, though some callers may duplicate the journaling. -* Journaling within the func just make the logic look more -* straightforward. -*/ - status =ocfs2_journal_access_di (handle, -INODE_CACHE (inode), - fe_bh, -OCFS2_JOURNAL_ACCESS_WRITE ); -if (status <0 ) { -mlog_errno (status); - goto leave; + goto rollback; } fe->i_flags |=cpu_to_le32 (OCFS2_ORPHANED_FL );
@@ -2057,6 +2057,13 @@ static int ocfs2_orphan_add(struct ocfs2_super *osb,trace_ocfs2_orphan_add_end ((unsigned long long )OCFS2_I (inode)->ip_blkno, osb->slot_num); +rollback: +if (status <0 ) { +if (S_ISDIR (inode->i_mode)) +ocfs2_add_links_count (orphan_fe,-1 ); +set_nlink (orphan_dir_inode,ocfs2_read_links_count (orphan_fe)); + } + leave:brelse (orphan_dir_bh);
Signature · 1 line
1.7.9.7
PATCH v2 1/1 ocfs2: need rollback when journal_access failed in ocfs2_orphan_add()
Quoted 8 lines · Younger Liu
While adding a file into orphan dir in
ocfs2_orphan_add(), it calls__ocfs2_add_entry()beforeocfs2_journal_access_di(). Ifocfs2_journal_access_di()failed, the file is added into orphan dir, and orphan dir dinode updated, but file dinode has not been updated.
Accordingly, the data is not consistent between file dinode and orphan dir.
Quoted 4 lines
So, need to call
ocfs2_journal_access_di()before__ocfs2_add_entry(), and ifocfs2_journal_access_di()failed,orphan_feandorphan_dir_inode->i_nlinkneed rollback.
This bug is introduced by commits 3939fda4.
Quoted 71 lines
Signed-off-by Younger Liu <[email protected]>Cc Jie Liu <[email protected]>--- fs/ocfs2/namei.c | 39 +++++++++++++++++++++++---------------- 1 file changed, 23 insertions(+), 16 deletions(-)fs/ocfs2/namei.c +23
-16@@ -2012,6 +2012,21 @@ static int ocfs2_orphan_add(struct ocfs2_super *osb, goto leave; } +/* +* We're going to journal the change of i_flags and i_orphaned_slot. +* It's safe anyway, though some callers may duplicate the journaling. +* Journaling within the func just make the logic look more +* straightforward. +*/ + status =ocfs2_journal_access_di (handle, +INODE_CACHE (inode), + fe_bh, +OCFS2_JOURNAL_ACCESS_WRITE ); +if (status <0 ) { +mlog_errno (status); + goto leave; + } +/* we're a cluster, and nlink can change on disk from * underneath us... */ orphan_fe = (struct ocfs2_dinode *) orphan_dir_bh->b_data;@@ -2026,22 +2041,7 @@ static int ocfs2_orphan_add(struct ocfs2_super *osb, orphan_dir_bh, lookup);if (status <0 ) {mlog_errno (status); - goto leave; - } - -/* -* We're going to journal the change of i_flags and i_orphaned_slot. -* It's safe anyway, though some callers may duplicate the journaling. -* Journaling within the func just make the logic look more -* straightforward. -*/ - status =ocfs2_journal_access_di (handle, -INODE_CACHE (inode), - fe_bh, -OCFS2_JOURNAL_ACCESS_WRITE ); -if (status <0 ) { -mlog_errno (status); - goto leave; + goto rollback; } fe->i_flags |=cpu_to_le32 (OCFS2_ORPHANED_FL );@@ -2057,6 +2057,13 @@ static int ocfs2_orphan_add(struct ocfs2_super *osb,trace_ocfs2_orphan_add_end ((unsigned long long )OCFS2_I (inode)->ip_blkno, osb->slot_num); +rollback: +if (status <0 ) { +if (S_ISDIR (inode->i_mode)) +ocfs2_add_links_count (orphan_fe,-1 ); +set_nlink (orphan_dir_inode,ocfs2_read_links_count (orphan_fe)); + } + leave:brelse (orphan_dir_bh);
PATCH v2 1/1 ocfs2: need rollback when journal_access failed in ocfs2_orphan_add()
In reply to Younger Liufs/ocfs2/namei.c static int ocfs2_orphan_add(struct ocfs2_super *osb,
Quoted 15 lines · On Thu, 20 Jun 2013 15:59:30 +0800 Younger Liu <[email protected]> wrote:
While adding a file into orphan dir in
ocfs2_orphan_add(), it calls__ocfs2_add_entry()beforeocfs2_journal_access_di(). Ifocfs2_journal_access_di()failed, the file is added into orphan dir, and orphan dir dinode updated, but file dinode has not been updated.
Accordingly, the data is not consistent between file dinode and orphan dir.So, need to call
ocfs2_journal_access_di()before__ocfs2_add_entry(), and ifocfs2_journal_access_di()failed,orphan_feandorphan_dir_inode->i_nlinkneed rollback.fs/ocfs2/namei.c +0
-0@@ -2012,6 +2012,21 @@ static int ocfs2_orphan_add(struct ocfs2_super *osb,
ocfs2_orphan_add() will call mlog_errno(status) two times for the same error in many cases. That's not a big problem, but is sloppy and asks for a cleanup.
PATCH v2 1/1 ocfs2: need rollback when journal_access failed in ocfs2_orphan_add()
Quoted 14 lines · Andrew Morton
Quoted 12 lines · On Thu, 20 Jun 2013 15:59:30 +0800 Younger Liu <[email protected]> wrote:
While adding a file into orphan dir in
ocfs2_orphan_add(), it calls__ocfs2_add_entry()beforeocfs2_journal_access_di(). Ifocfs2_journal_access_di()failed, the file is added into orphan dir, and orphan dir dinode updated, but file dinode has not been updated.
Accordingly, the data is not consistent between file dinode and orphan dir.So, need to call
ocfs2_journal_access_di()before__ocfs2_add_entry(), and ifocfs2_journal_access_di()failed,orphan_feandorphan_dir_inode->i_nlinkneed rollback.
Quoted 10 lines
fs/ocfs2/namei.c static int ocfs2_orphan_add(struct ocfs2_super *osb,
Quoted 3 lines
fs/ocfs2/namei.c +0
-0@@ -2012,6 +2012,21 @@ static int ocfs2_orphan_add(struct ocfs2_super *osb,
ocfs2_orphan_add()will callmlog_errno(status)two times for the same error in many cases. That's not a big problem, but is sloppy and asks for a cleanup.
Thanks for your review, I will resent the patch in a moment.
Younger