From: syzbot <syzbot+a9850b21d99643eadbb8@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
clang-built-linux@googlegroups.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
nathan@kernel.org, ndesaulniers@google.com,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
tintinm2017@gmail.com
Subject: Re: [syzbot] [ntfs3?] WARNING in attr_data_get_block (3)
Date: Wed, 22 Nov 2023 06:48:13 -0800 [thread overview]
Message-ID: <000000000000ff9bd1060abececf@google.com> (raw)
In-Reply-To: <0000000000009b49ce0606fd665a@google.com>
syzbot suspects this issue was fixed by commit:
commit 4ad5c924df6cd6d85708fa23f9d9a2b78a2e428e
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Sep 22 10:07:59 2023 +0000
fs/ntfs3: Allow repeated call to ntfs3_put_sbi
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17484614e80000
start commit: e402b08634b3 Merge tag 'soc-fixes-6.6' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=12da82ece7bf46f9
dashboard link: https://syzkaller.appspot.com/bug?extid=a9850b21d99643eadbb8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12b684e6680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10ede4d6680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Allow repeated call to ntfs3_put_sbi
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-11-22 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 19:47 [syzbot] [ntfs3?] WARNING in attr_data_get_block (3) syzbot
2023-11-22 14: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=000000000000ff9bd1060abececf@google.com \
--to=syzbot+a9850b21d99643eadbb8@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tintinm2017@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).