From: Alexander Potapenko <glider@google.com>
To: syzbot <syzbot+6c0effb5877f6b0344e2@syzkaller.appspotmail.com>
Cc: David Miller <davem@davemloft.net>,
hverkuil@xs4all.nl, linux-can@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-media@vger.kernel.org, mchehab@kernel.org,
mchehab@s-opensource.com, mkl@pengutronix.de,
Networking <netdev@vger.kernel.org>,
socketcan@hartkopp.net,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: kernel BUG at arch/x86/mm/physaddr.c:LINE! (2)
Date: Thu, 4 Apr 2019 16:47:00 +0200 [thread overview]
Message-ID: <CAG_fn=VnXmDSc_QNqyEv7f7iwHXC6taBq1t55fHWZpLZ0EdiNw@mail.gmail.com> (raw)
In-Reply-To: <000000000000462a4105848c8e12@google.com>
On Wed, Mar 20, 2019 at 9:35 PM syzbot
<syzbot+6c0effb5877f6b0344e2@syzkaller.appspotmail.com> wrote:
>
> syzbot has bisected this bug to:
>
> commit 6d469a202ee73196d0df76025af80bd6a379e658
> Author: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> Date: Sun May 14 17:07:21 2017 +0000
>
> Merge tag 'v4.12-rc1' into patchwork
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12639fd7200000
> start commit: 6d469a20 Merge tag 'v4.12-rc1' into patchwork
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=15639fd7200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=11639fd7200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=d86f24333880b605
> dashboard link: https://syzkaller.appspot.com/bug?extid=6c0effb5877f6b0344e2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1312062b400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=131bd093400000
>
> Reported-by: syzbot+6c0effb5877f6b0344e2@syzkaller.appspotmail.com
> Fixes: 6d469a20 ("Merge tag 'v4.12-rc1' into patchwork")
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/000000000000462a4105848c8e12%40google.com.
> For more options, visit https://groups.google.com/d/optout.
I believe this bug is caused by vivid_vid_cap_s_selection() calling
kfree(dev->bitmap_cap).
This makes little sense, as dev->bitmap_cap seems to be allocated
using vzalloc().
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
next prev parent reply other threads:[~2019-04-04 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 23:32 kernel BUG at arch/x86/mm/physaddr.c:LINE! (2) syzbot
2018-11-18 20:09 ` syzbot
2019-03-20 20:35 ` syzbot
2019-04-04 14:47 ` Alexander Potapenko [this message]
2019-04-04 14:51 ` Hans Verkuil
2019-04-04 14:54 ` Alexander Potapenko
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='CAG_fn=VnXmDSc_QNqyEv7f7iwHXC6taBq1t55fHWZpLZ0EdiNw@mail.gmail.com' \
--to=glider@google.com \
--cc=davem@davemloft.net \
--cc=hverkuil@xs4all.nl \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=syzbot+6c0effb5877f6b0344e2@syzkaller.appspotmail.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 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).