From: syzbot <syzbot+60cf892fc31d1f4358fc@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, astrajoan@yahoo.com,
ivan.orlov0322@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
skhan@linuxfoundation.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in hdr_find_e (2)
Date: Wed, 09 Aug 2023 13:49:25 -0700 [thread overview]
Message-ID: <0000000000006ca4a20602839deb@google.com> (raw)
In-Reply-To: <20230809191118.30721-1-astrajoan@yahoo.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+60cf892fc31d1f4358fc@syzkaller.appspotmail.com
Tested on:
commit: cacc6e22 tpm: Add a helper for checking hwrng enabled
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1107f5a5a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=171b698bc2e613cf
dashboard link: https://syzkaller.appspot.com/bug?extid=60cf892fc31d1f4358fc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=11e4f5fda80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-08-09 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230809191118.30721-1-astrajoan@yahoo.com>
2023-08-09 20:49 ` syzbot [this message]
2023-08-03 9:29 [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in hdr_find_e (2) syzbot
2023-08-31 0:31 ` 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=0000000000006ca4a20602839deb@google.com \
--to=syzbot+60cf892fc31d1f4358fc@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=astrajoan@yahoo.com \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--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).