[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69575097.050a0220.a1b6.034e.GAE@google.com>
Date: Thu, 01 Jan 2026 20:59:03 -0800
From: syzbot <syzbot+3e58a7dc1a8c00243999@...kaller.appspotmail.com>
To: almaz.alexandrovich@...agon-software.com, dan.carpenter@...aro.org,
eadavis@...com, kartikey406@...il.com, linux-kernel@...r.kernel.org,
lkp@...el.com, ntfs3@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
oe-kbuild@...ts.linux.dev, penguin-kernel@...ove.sakura.ne.jp,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [ntfs3?] INFO: trying to register non-static key in ntfs_setattr
syzbot suspects this issue was fixed by commit:
commit be99c62ac7e7af514e4b13f83c891a3cccefaa48
Author: Edward Adam Davis <eadavis@...com>
Date: Tue Sep 16 05:50:13 2025 +0000
ntfs3: init run lock for extend inode
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113ff222580000
start commit: 98906f9d850e Merge tag 'rtc-6.18' of git://git.kernel.org/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=af9170887d81dea1
dashboard link: https://syzkaller.appspot.com/bug?extid=3e58a7dc1a8c00243999
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f4e542580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e5e9e2580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ntfs3: init run lock for extend inode
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Powered by blists - more mailing lists