From: syzbot <syzbot+2f012b85ac8ce9be92e5@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
hverkuil-cisco@xs4all.nl, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mchehab@kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] general protection fault in d_flags_for_inode
Date: Thu, 13 Jul 2023 02:37:26 -0700 [thread overview]
Message-ID: <00000000000085151506005b1491@google.com> (raw)
In-Reply-To: <00000000000009408f05e977da5d@google.com>
syzbot suspects this issue was fixed by commit:
commit c43784c856483dded7956175b5786e27af6d87f1
Author: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Date: Thu Dec 8 07:51:32 2022 +0000
media: v4l2-mem2mem: use vb2_is_streaming()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17e7d1bca80000
start commit: 4da34b7d175d Merge tag 'thermal-6.1-rc2' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ea03ca45176080bc
dashboard link: https://syzkaller.appspot.com/bug?extid=2f012b85ac8ce9be92e5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17834f9a880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10edf526880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: media: v4l2-mem2mem: use vb2_is_streaming()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2023-07-13 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000009408f05e977da5d@google.com>
2023-07-13 9:37 ` syzbot [this message]
2023-07-13 10:17 ` [syzbot] [ntfs3?] general protection fault in d_flags_for_inode Aleksandr Nogikh
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=00000000000085151506005b1491@google.com \
--to=syzbot+2f012b85ac8ce9be92e5@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.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 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).