From: syzbot <syzbot+5b2f934f08ab03d473ff@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] WARNING in wnd_add_free_ext (2)
Date: Thu, 10 Aug 2023 15:14:38 -0700 [thread overview]
Message-ID: <00000000000003f591060298ecc6@google.com> (raw)
In-Reply-To: <00000000000040e14205ffbf333f@google.com>
syzbot has bisected this issue to:
commit 3880f2b816a7e4ca889b7e8a42e6c62c5706ed36
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Mon Oct 25 15:31:28 2021 +0000
fs/ntfs3: Fix fiemap + fix shrink file size (to remove preallocated space)
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=168fd89ba80000
start commit: f6a691685962 Merge tag '6.5-rc4-smb3-client-fix' of git://..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=158fd89ba80000
console output: https://syzkaller.appspot.com/x/log.txt?x=118fd89ba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1e3d5175079af5a4
dashboard link: https://syzkaller.appspot.com/bug?extid=5b2f934f08ab03d473ff
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13f56679a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=118b8eeda80000
Reported-by: syzbot+5b2f934f08ab03d473ff@syzkaller.appspotmail.com
Fixes: 3880f2b816a7 ("fs/ntfs3: Fix fiemap + fix shrink file size (to remove preallocated space)")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-10 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 15:39 [syzbot] [ntfs3?] WARNING in wnd_add_free_ext (2) syzbot
2023-08-06 3:48 ` syzbot
2023-08-10 22:14 ` syzbot [this message]
2023-11-20 23:01 ` 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=00000000000003f591060298ecc6@google.com \
--to=syzbot+5b2f934f08ab03d473ff@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--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.