From: Pavel Machek <pavel@ucw.cz>
To: syzbot <syzbot+e1a4f80c370d2381e49f@syzkaller.appspotmail.com>
Cc: Julia.Lawall@lip6.fr, bp@alien8.de, dan.j.williams@intel.com,
dave.hansen@linux.intel.com, dave.jiang@intel.com,
haozhong.zhang@intel.com, hpa@zytor.com,
jacek.anaszewski@gmail.com, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
pbonzini@redhat.com, peterz@infradead.org, rkrcmar@redhat.com,
rpurdie@rpsys.net, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: WARNING in untrack_pfn
Date: Fri, 12 Apr 2019 15:01:12 +0200 [thread overview]
Message-ID: <20190412130112.GA8384@amd> (raw)
In-Reply-To: <0000000000007b03eb058653caea@google.com>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
On Fri 2019-04-12 04:42:01, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit c68729119f4d2993bec3c9cb999ad76de5aeddba
> Author: Julia Lawall <Julia.Lawall@lip6.fr>
> Date: Sat Jul 15 09:58:19 2017 +0000
>
> leds: tlc591xx: add missing of_node_put
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12cda0f3200000
> start commit: 23203e3f Merge branch 'akpm' (patches from Andrew)
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=11cda0f3200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=16cda0f3200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=861a3573f4e78ba1
> dashboard link: https://syzkaller.appspot.com/bug?extid=e1a4f80c370d2381e49f
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17836d15400000
>
> Reported-by: syzbot+e1a4f80c370d2381e49f@syzkaller.appspotmail.com
> Fixes: c68729119f4d ("leds: tlc591xx: add missing of_node_put")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Can you revert c68729119f4d2993bec3c9cb999ad76de5aeddba on master and
see if it fixes the problem? Because this is hard to believe...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-04-12 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000f70a0e0571ad8ffb@google.com>
2019-04-12 11:42 ` WARNING in untrack_pfn syzbot
2019-04-12 13:01 ` Pavel Machek [this message]
2019-04-12 13:21 ` Julia Lawall
2019-05-08 12:37 ` Dmitry Vyukov
2019-08-13 10:56 ` syzbot
2019-08-13 11:31 ` Pavel Machek
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=20190412130112.GA8384@amd \
--to=pavel@ucw.cz \
--cc=Julia.Lawall@lip6.fr \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=haozhong.zhang@intel.com \
--cc=hpa@zytor.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=rpurdie@rpsys.net \
--cc=syzbot+e1a4f80c370d2381e49f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).