From: Prithvi Tambewagh <activprithvi@gmail.com>
To: syzbot+78359d5fbb04318c35e9@syzkaller.appspotmail.com,
jlbec@evilplan.org, joseph.qi@linux.alibaba.com, mark@fasheh.com
Cc: heming.zhao@suse.com, linux-kernel@vger.kernel.org,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com,
Prithvi Tambewagh <activprithvi@gmail.com>
Subject: Syzbot test for ocfs2: Fix deadlock in ocfs2_del_inode_from_orphan
Date: Tue, 6 Jan 2026 17:00:53 +0530 [thread overview]
Message-ID: <20260106113053.284336-1-activprithvi@gmail.com> (raw)
In-Reply-To: <66fdfef3.050a0220.9ec68.0031.GAE@google.com>
#syz test upstream 765e56e41a5af2d456ddda6cbd617b9d3295ab4e
Signed-off-by: Prithvi Tambewagh <activprithvi@gmail.com>
---
fs/ocfs2/aops.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/ocfs2/aops.c b/fs/ocfs2/aops.c
index 76c86f1c2b1c..586e3b74d782 100644
--- a/fs/ocfs2/aops.c
+++ b/fs/ocfs2/aops.c
@@ -2295,8 +2295,6 @@ static int ocfs2_dio_end_io_write(struct inode *inode,
goto out;
}
- down_write(&oi->ip_alloc_sem);
-
/* Delete orphan before acquire i_rwsem. */
if (dwc->dw_orphaned) {
BUG_ON(dwc->dw_writer_pid != task_pid_nr(current));
@@ -2309,6 +2307,8 @@ static int ocfs2_dio_end_io_write(struct inode *inode,
mlog_errno(ret);
}
+ down_write(&oi->ip_alloc_sem);
+
di = (struct ocfs2_dinode *)di_bh->b_data;
ocfs2_init_dinode_extent_tree(&et, INODE_CACHE(inode), di_bh);
base-commit: 765e56e41a5af2d456ddda6cbd617b9d3295ab4e
--
2.34.1
next prev parent reply other threads:[~2026-01-06 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 2:18 [syzbot] [ocfs2?] possible deadlock in ocfs2_del_inode_from_orphan syzbot
2024-12-19 8:16 ` syzbot
2026-01-06 11:30 ` Prithvi Tambewagh [this message]
2026-01-06 11:59 ` syzbot
2026-02-23 3:38 ` Forwarded: Syzbot test for v2: ocfs2: clear lock identity upon inode eviction syzbot
2026-02-23 4:31 ` syzbot
2026-02-24 5:28 ` Forwarded: test patch syzbot
2026-02-24 6:35 ` syzbot
2026-03-02 5:31 ` 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=20260106113053.284336-1-activprithvi@gmail.com \
--to=activprithvi@gmail.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+78359d5fbb04318c35e9@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.