From: syzbot <syzbot+8e034d7422d389827720@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mail@seo-local.net, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] WARNING in attr_data_get_block (4)
Date: Mon, 11 Nov 2024 19:23:06 -0800 [thread overview]
Message-ID: <6732ca1a.050a0220.1fb99c.0162.GAE@google.com> (raw)
In-Reply-To: <000000000000307a8e0615918f2b@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=17d5b8c0580000
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=8e034d7422d389827720
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=171bf3a9180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1084f189180000
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-12 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 8:26 [syzbot] [ntfs3?] WARNING in attr_data_get_block (4) syzbot
2024-11-12 3:23 ` 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=6732ca1a.050a0220.1fb99c.0162.GAE@google.com \
--to=syzbot+8e034d7422d389827720@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@seo-local.net \
--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;
as well as URLs for NNTP newsgroup(s).