From: syzbot <syzbot+2e842ec1beb075a25865@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] INFO: trying to register non-static key in ntfs3_setattr (2)
Date: Tue, 05 Nov 2024 01:01:02 -0800 [thread overview]
Message-ID: <6729dece.050a0220.2edce.1507.GAE@google.com> (raw)
In-Reply-To: <66ebefad.050a0220.92ef1.0019.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 1fd21919de6de245b63066b8ee3cfba92e36f0e9
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Thu Aug 22 11:43:32 2024 +0000
fs/ntfs3: Stale inode instead of bad
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=122d3587980000
start commit: 0babf683783d Merge tag 'pinctrl-v6.11-4' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1c9e296880039df9
dashboard link: https://syzkaller.appspot.com/bug?extid=2e842ec1beb075a25865
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b9b0a9980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=155e9900580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Stale inode instead of bad
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-11-05 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 9:32 [syzbot] [ntfs3?] INFO: trying to register non-static key in ntfs3_setattr (2) syzbot
2024-11-05 9:01 ` syzbot [this message]
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=6729dece.050a0220.2edce.1507.GAE@google.com \
--to=syzbot+2e842ec1beb075a25865@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--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