The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+6bf948e47f9bac7aacfa@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [ocfs2?] possible deadlock in __ocfs2_flush_truncate_log
Date: Fri, 04 Jul 2025 20:03:53 -0700	[thread overview]
Message-ID: <68689619.a00a0220.c7b3.002b.GAE@google.com> (raw)
In-Reply-To: <67d5645c.050a0220.1dc86f.0004.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: Re: [syzbot] [ocfs2?] possible deadlock in __ocfs2_flush_truncate_log
Author: ipravdin.official@gmail.com

#syz test

diff --git a/fs/ocfs2/move_extents.c b/fs/ocfs2/move_extents.c
index 369c7d27befd..ab460cb2c9c8 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.
@@ -637,8 +639,6 @@ static int ocfs2_move_extent(struct ocfs2_move_extents_context *context,
                goto out_unlock_gb_mutex;
        }

-       inode_lock(tl_inode);
-
        handle = ocfs2_start_trans(osb, credits);
        if (IS_ERR(handle)) {
                ret = PTR_ERR(handle);

	Ivan Pravdin

  reply	other threads:[~2025-07-05  3:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15 11:28 [syzbot] [ocfs2?] possible deadlock in __ocfs2_flush_truncate_log syzbot
2025-07-05  3:03 ` syzbot [this message]
2025-07-05  3:16 ` syzbot
     [not found] <kl7jac3bqyd3dz4uj5rp3dwam6rdbegvf5qahgn7njdaeodndj@aq7yil27yawv>
2025-07-05  3:06 ` syzbot
2025-07-05  3:10   ` Ivan Pravdin
2025-07-05  3:12     ` syzbot
     [not found] <srmiqb5n6iqsxric6cbkrpinsfcblpowhpijfzjjakiyhs4och@2vrutii673vc>
2025-07-05  3:42 ` syzbot

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=68689619.a00a0220.c7b3.002b.GAE@google.com \
    --to=syzbot+6bf948e47f9bac7aacfa@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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