From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Ivan Pravdin <ipravdin.official@gmail.com>,
mark@fasheh.com, jlbec@evilplan.org, ocfs2-devel@lists.linux.dev,
linux-kernel@vger.kernel.org, akpm <akpm@linux-foundation.org>
Cc: syzbot+6bf948e47f9bac7aacfa@syzkaller.appspotmail.com
Subject: Re: [PATCH v4] ocfs2: avoid potential ABBA deadlock by reordering tl_inode lock
Date: Tue, 8 Jul 2025 10:13:14 +0800 [thread overview]
Message-ID: <c4f6e4a2-1127-43a0-8566-3c493a2795fe@linux.alibaba.com> (raw)
In-Reply-To: <20250708020640.387741-1-ipravdin.official@gmail.com>
On 2025/7/8 10:06, Ivan Pravdin wrote:
> In ocfs2_move_extent(), tl_inode is currently locked after the global
> bitmap inode. However, in ocfs2_flush_truncate_log(), the lock order
> is reversed: tl_inode is locked first, followed by the global bitmap
> inode.
>
> This creates a classic ABBA deadlock scenario if two threads attempt
> these operations concurrently and acquire the locks in different orders.
>
> To prevent this, move the tl_inode locking earlier in
> ocfs2_move_extent(), so that it always precedes the global bitmap
> inode lock.
>
> No functional changes beyond lock ordering.
>
> Reported-by: syzbot+6bf948e47f9bac7aacfa@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/all/67d5645c.050a0220.1dc86f.0004.GAE@google.com/
> Signed-off-by: Ivan Pravdin <ipravdin.official@gmail.com>
Looks fine.
Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> v1 -> v2: Fixed unlocking order in ocfs2_move_extent.
> v2 -> v3: Added missing out_unlock_tl_inode and renamed out_unlock_gb_mutex to
> out_unlock_gb_inode and out_unlock_gb_inode to out_unlock.
> v3 -> v4: Rearranged gb_inode cleanup.
>
> fs/ocfs2/move_extents.c | 19 +++++++++----------
> 1 file changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/fs/ocfs2/move_extents.c b/fs/ocfs2/move_extents.c
> index 369c7d27befd..cbe2f8ed8897 100644
> --- a/fs/ocfs2/move_extents.c
> +++ b/fs/ocfs2/move_extents.c
> @@ -617,6 +617,8 @@ static int ocfs2_move_extent(struct ocfs2_move_extents_context *context,
> */
> credits += OCFS2_INODE_UPDATE_CREDITS + 1;
>
> + inode_lock(tl_inode);
> +
> /*
> * ocfs2_move_extent() didn't reserve any clusters in lock_allocators()
> * logic, while we still need to lock the global_bitmap.
> @@ -626,7 +628,7 @@ static int ocfs2_move_extent(struct ocfs2_move_extents_context *context,
> if (!gb_inode) {
> mlog(ML_ERROR, "unable to get global_bitmap inode\n");
> ret = -EIO;
> - goto out;
> + goto out_unlock_tl_inode;
> }
>
> inode_lock(gb_inode);
> @@ -634,16 +636,14 @@ static int ocfs2_move_extent(struct ocfs2_move_extents_context *context,
> ret = ocfs2_inode_lock(gb_inode, &gb_bh, 1);
> if (ret) {
> mlog_errno(ret);
> - goto out_unlock_gb_mutex;
> + goto out_unlock_gb_inode;
> }
>
> - inode_lock(tl_inode);
> -
> handle = ocfs2_start_trans(osb, credits);
> if (IS_ERR(handle)) {
> ret = PTR_ERR(handle);
> mlog_errno(ret);
> - goto out_unlock_tl_inode;
> + goto out_unlock;
> }
>
> new_phys_blkno = ocfs2_clusters_to_blocks(inode->i_sb, *new_phys_cpos);
> @@ -703,15 +703,14 @@ static int ocfs2_move_extent(struct ocfs2_move_extents_context *context,
> out_commit:
> ocfs2_commit_trans(osb, handle);
> brelse(gd_bh);
> -
> -out_unlock_tl_inode:
> - inode_unlock(tl_inode);
> -
> +out_unlock:
> ocfs2_inode_unlock(gb_inode, 1);
> -out_unlock_gb_mutex:
> +out_unlock_gb_inode:
> inode_unlock(gb_inode);
> brelse(gb_bh);
> iput(gb_inode);
> +out_unlock_tl_inode:
> + inode_unlock(tl_inode);
>
> out:
> if (context->meta_ac) {
prev parent reply other threads:[~2025-07-08 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 2:06 Ivan Pravdin
2025-07-08 2:13 ` Joseph Qi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4f6e4a2-1127-43a0-8566-3c493a2795fe@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=ipravdin.official@gmail.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+6bf948e47f9bac7aacfa@syzkaller.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®