From: syzbot <syzbot+3e58a7dc1a8c00243999@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
dan.carpenter@linaro.org, eadavis@qq.com, kartikey406@gmail.com,
linux-kernel@vger.kernel.org, lkp@intel.com,
ntfs3@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
oe-kbuild@lists.linux.dev, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] INFO: trying to register non-static key in ntfs_setattr
Date: Thu, 01 Jan 2026 20:59:03 -0800 [thread overview]
Message-ID: <69575097.050a0220.a1b6.034e.GAE@google.com> (raw)
In-Reply-To: <68ed7606.a70a0220.b3ac9.001f.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit be99c62ac7e7af514e4b13f83c891a3cccefaa48
Author: Edward Adam Davis <eadavis@qq.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
next prev parent reply other threads:[~2026-01-02 4:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 21:58 [syzbot] [ntfs3?] INFO: trying to register non-static key in ntfs_setattr syzbot
2025-10-14 6:41 ` Forwarded: [PATCH] ntfs3: initialize run_lock for MFT inode in ntfs_read_mft syzbot
2025-10-14 7:38 ` Forwarded: [PATCH] ntfs3: prevent MFT inode resize operations syzbot
2025-10-14 9:06 ` Forwarded: [PATCH] ntfs3: add debug warnings for run_lock initialization syzbot
2025-10-14 9:43 ` syzbot
2025-10-14 10:09 ` syzbot
2025-10-14 11:02 ` syzbot
2025-10-14 11:49 ` syzbot
2025-10-16 17:58 ` Dan Carpenter
2025-10-14 12:53 ` Forwarded: [PATCH] ntfs3: initialize run_lock for $Extend inode records syzbot
2025-10-14 13:25 ` Forwarded: [PATCH] ntfs3: prevent operations on NTFS system files syzbot
2026-01-02 4:59 ` syzbot [this message]
2026-01-02 5:17 ` [syzbot] [ntfs3?] INFO: trying to register non-static key in ntfs_setattr Tetsuo Handa
[not found] <20251014064114.10250-1-kartikey406@gmail.com>
2025-10-14 7:17 ` syzbot
[not found] <20251014073834.12992-1-kartikey406@gmail.com>
2025-10-14 8:13 ` syzbot
[not found] <20251014090554.628056-1-kartikey406@gmail.com>
2025-10-14 9:29 ` syzbot
[not found] <20251014094307.630590-1-kartikey406@gmail.com>
2025-10-14 10:12 ` syzbot
[not found] <20251014100933.632340-1-kartikey406@gmail.com>
2025-10-14 10:30 ` syzbot
[not found] <20251014110217.635610-1-kartikey406@gmail.com>
2025-10-14 11:36 ` syzbot
[not found] <20251014114858.637382-1-kartikey406@gmail.com>
2025-10-14 12:14 ` syzbot
[not found] <20251014125319.639727-1-kartikey406@gmail.com>
2025-10-14 13:34 ` syzbot
[not found] <20251014132504.642005-1-kartikey406@gmail.com>
2025-10-14 13:57 ` 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=69575097.050a0220.a1b6.034e.GAE@google.com \
--to=syzbot+3e58a7dc1a8c00243999@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=dan.carpenter@linaro.org \
--cc=eadavis@qq.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ntfs3@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox