From: syzbot <syzbot+29dc75ed37be943c610e@syzkaller.appspotmail.com>
To: adilger@dilger.ca, almaz.alexandrovich@paragon-software.com,
edward.lo@ambergroup.io, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
nathan@kernel.org, ndesaulniers@google.com,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
trix@redhat.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in __d_instantiate
Date: Fri, 15 Sep 2023 12:01:29 -0700 [thread overview]
Message-ID: <000000000000925bf206056a6b69@google.com> (raw)
In-Reply-To: <0000000000005c2d1f05e8945724@google.com>
syzbot suspects this issue was fixed by commit:
commit 54e45702b648b7c0000e90b3e9b890e367e16ea8
Author: Edward Lo <edward.lo@ambergroup.io>
Date: Thu Sep 22 16:50:23 2022 +0000
fs/ntfs3: Validate resident attribute name
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12403c74680000
start commit: f9ff5644bcc0 Merge tag 'hsi-for-6.2' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c163713cf9186fe7
dashboard link: https://syzkaller.appspot.com/bug?extid=29dc75ed37be943c610e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1077def7880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10175baf880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Validate resident attribute name
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-09-15 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 19:51 [syzbot] BUG: unable to handle kernel NULL pointer dereference in __d_instantiate syzbot
2022-09-13 20:14 ` Andreas Dilger
2022-09-13 21:27 ` Al Viro
2023-09-15 19:01 ` 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=000000000000925bf206056a6b69@google.com \
--to=syzbot+29dc75ed37be943c610e@syzkaller.appspotmail.com \
--cc=adilger@dilger.ca \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=edward.lo@ambergroup.io \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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.