From: syzbot <syzbot+04cf7b83f6dd2c3a54c8@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, eadavis@sina.com,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] general protection fault in al_destroy
Date: Wed, 02 Sep 2026 20:44:03 -0700 [thread overview]
Message-ID: <6a98ed03.2e567484.299ffc.0006.GAE@google.com> (raw)
In-Reply-To: <6a778cfb.9c11d2ce.289b96.00b8.GAE@google.com>
syzbot has bisected this issue to:
commit be310476e8868ebe7a2ce8fb0e7b229535723963
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Thu Jul 30 08:47:44 2026 +0000
fs/ntfs3: Add basic support for alternative data streams
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17621f79580000
start commit: 73e3f0710014 Merge tag 'nfs-for-7.3-1' of git://git.linux-..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14e21f79580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10e21f79580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9efed59cf70d6280
dashboard link: https://syzkaller.appspot.com/bug?extid=04cf7b83f6dd2c3a54c8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1391859e580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11417415580000
Reported-by: syzbot+04cf7b83f6dd2c3a54c8@syzkaller.appspotmail.com
Fixes: be310476e886 ("fs/ntfs3: Add basic support for alternative data streams")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2026-09-03 3:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 20:09 [syzbot] [ntfs3?] general protection fault in al_destroy syzbot
2026-08-27 5:32 ` syzbot
2026-08-27 8:15 ` [PATCH] fs/ntfs3: Refine the ni cleanup Edward Adam Davis
2026-08-27 9:43 ` [PATCH v2] " Edward Adam Davis
2026-09-03 3:44 ` 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=6a98ed03.2e567484.299ffc.0006.GAE@google.com \
--to=syzbot+04cf7b83f6dd2c3a54c8@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=eadavis@sina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.