All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6bed2d543cf7e48b822b@syzkaller.appspotmail.com>
To: ezequiel@collabora.com, laurent.pinchart@ideasonboard.com,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	mchehab+huawei@kernel.org, mchehab@kernel.org,
	sakari.ailus@linux.intel.com, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: null-ptr-deref Write in media_request_close
Date: Thu, 18 Jun 2020 10:56:04 -0700	[thread overview]
Message-ID: <0000000000007e5a7305a85f7dbd@google.com> (raw)
In-Reply-To: <000000000000aa674005a845bbc5@google.com>

syzbot has bisected this bug to:

commit 016baa59bf9f6c2550480b73f18100285e3a4fd2
Author: Ezequiel Garcia <ezequiel@collabora.com>
Date:   Tue Apr 14 22:06:24 2020 +0000

    media: Kconfig: Don't expose the Request API option

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=108d7149100000
start commit:   7ae77150 Merge tag 'powerpc-5.8-1' of git://git.kernel.org..
git tree:       upstream
final crash:    https://syzkaller.appspot.com/x/report.txt?x=128d7149100000
console output: https://syzkaller.appspot.com/x/log.txt?x=148d7149100000
kernel config:  https://syzkaller.appspot.com/x/.config?x=be4578b3f1083656
dashboard link: https://syzkaller.appspot.com/bug?extid=6bed2d543cf7e48b822b
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17b3fc35100000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12fbb6f1100000

Reported-by: syzbot+6bed2d543cf7e48b822b@syzkaller.appspotmail.com
Fixes: 016baa59bf9f ("media: Kconfig: Don't expose the Request API option")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2020-06-18 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 11:12 KASAN: null-ptr-deref Write in media_request_close syzbot
2020-06-18 14:11 ` syzbot
2020-06-18 17:56 ` syzbot [this message]
     [not found] ` <CAAEAJfAOnTv1J-iSqEo3JdHr-JOZyWVGZcjnduJQOqaVhhx3kw@mail.gmail.com>
2020-06-19 14:14   ` Ricardo Cañuelo

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=0000000000007e5a7305a85f7dbd@google.com \
    --to=syzbot+6bed2d543cf7e48b822b@syzkaller.appspotmail.com \
    --cc=ezequiel@collabora.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --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 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.