linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+c0b807de416427ff3dd1@syzkaller.appspotmail.com>
To: a@unstable.cc, akpm@osdl.org, arvind.yadav.cs@gmail.com,
	 b.a.t.m.a.n@lists.open-mesh.org, davem@davemloft.net,
	kgene@kernel.org,  krzk@kernel.org, kyungmin.park@samsung.com,
	 linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,  linux-media@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org,  mareklindner@neomailbox.ch,
	mchehab@kernel.org, mchehab@s-opensource.com,  mingo@kernel.org,
	netdev@vger.kernel.org, oleg@tv-sign.ru, roland@redhat.com,
	 s.nawrocki@samsung.com, sven@narfation.org,
	sw@simonwunderlich.de,  syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: WARNING in batadv_iv_send_outstanding_bat_ogm_packet
Date: Sun, 13 Oct 2019 20:57:01 -0700	[thread overview]
Message-ID: <0000000000002ba5570594d6dc99@google.com> (raw)
In-Reply-To: <00000000000059b6d40594d0f776@google.com>

syzbot has bisected this bug to:

commit 26d051e301f67cdd2ea3404abb43902f13214efa
Author: Arvind Yadav <arvind.yadav.cs@gmail.com>
Date:   Thu Jun 29 08:21:35 2017 +0000

     media: exynos4-is: fimc-is-i2c: constify dev_pm_ops structures

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10a0aff0e00000
start commit:   da940012 Merge tag 'char-misc-5.4-rc3' of git://git.kernel..
git tree:       upstream
final crash:    https://syzkaller.appspot.com/x/report.txt?x=12a0aff0e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14a0aff0e00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2d2fd92a28d3e50
dashboard link: https://syzkaller.appspot.com/bug?extid=c0b807de416427ff3dd1
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=141ffd77600000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11edd580e00000

Reported-by: syzbot+c0b807de416427ff3dd1@syzkaller.appspotmail.com
Fixes: 26d051e301f6 ("media: exynos4-is: fimc-is-i2c: constify dev_pm_ops  
structures")

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

           reply	other threads:[~2019-10-14  3:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <00000000000059b6d40594d0f776@google.com>]

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=0000000000002ba5570594d6dc99@google.com \
    --to=syzbot+c0b807de416427ff3dd1@syzkaller.appspotmail.com \
    --cc=a@unstable.cc \
    --cc=akpm@osdl.org \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=davem@davemloft.net \
    --cc=kgene@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mareklindner@neomailbox.ch \
    --cc=mchehab@kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    --cc=roland@redhat.com \
    --cc=s.nawrocki@samsung.com \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    --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 NNTP newsgroup(s).