linux-kernel - Re: [syzbot] [nilfs?] possible deadlock in nilfs_segctor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <tencent_C2C42D3D6D8894E8E82EECD6CD707A026F0A@qq.com>
Date: Fri,  9 May 2025 21:29:10 +0800
From: Edward Adam Davis <eadavis@...com>
To: syzbot+81394db39b0e2ed2db06@...kaller.appspotmail.com
Cc: linux-kernel@...r.kernel.org,
	syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [nilfs?] possible deadlock in nilfs_segctor_construct

#syz test

diff --git a/fs/nilfs2/segment.c b/fs/nilfs2/segment.c
index 83970d97840b..d3076015771f 100644
--- a/fs/nilfs2/segment.c
+++ b/fs/nilfs2/segment.c
@@ -2582,8 +2582,8 @@ static void nilfs_segctor_thread_construct(struct nilfs_sc_info *sci, int mode)
 {
 	struct nilfs_transaction_info ti;
 
-	nilfs_transaction_lock(sci->sc_super, &ti, 0);
 	nilfs_segctor_construct(sci, mode);
+	nilfs_transaction_lock(sci->sc_super, &ti, 0);
 
 	/*
 	 * Unclosed segment should be retried.  We do this using sc_timer.