From: syzbot <syzbot+06cc05ddc896f12b7ec5@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, amir73il@gmail.com,
christian@brauner.io, hdanton@sina.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
viro@ZenIV.linux.org.uk, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] kernel BUG in dnotify_free_mark
Date: Mon, 15 Sep 2025 00:48:02 -0700 [thread overview]
Message-ID: <68c7c4b2.050a0220.2ff435.0391.GAE@google.com> (raw)
In-Reply-To: <0000000000008b529305ec20dacc@google.com>
syzbot suspects this issue was fixed by commit:
commit 55ad333de0f80bc0caee10c6c27196cdcf8891bb
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Mon Dec 30 07:34:08 2024 +0000
fs/ntfs3: Unify inode corruption marking with _ntfs_bad_inode()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15420e42580000
start commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1a07d5da4eb21586
dashboard link: https://syzkaller.appspot.com/bug?extid=06cc05ddc896f12b7ec5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e3dffd180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f9e08d180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Unify inode corruption marking with _ntfs_bad_inode()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-09-15 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 23:45 [syzbot] kernel BUG in dnotify_free_mark syzbot
2022-10-31 17:50 ` Jan Kara
2022-10-31 18:18 ` Amir Goldstein
2022-11-01 10:57 ` Jan Kara
2025-09-15 7:48 ` 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=68c7c4b2.050a0220.2ff435.0391.GAE@google.com \
--to=syzbot+06cc05ddc896f12b7ec5@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=amir73il@gmail.com \
--cc=christian@brauner.io \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).