[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e3d9d95fd07502cccf8ef97ba7b2e2adb4eefbb3.camel@baylibre.com>
Date: Mon, 25 Mar 2019 12:54:49 +0100
From: Jerome Brunet <jbrunet@...libre.com>
To: syzbot <syzbot+f3e3434787332dfc1c47@...kaller.appspotmail.com>,
davem@...emloft.net, devicetree@...r.kernel.org,
khilman@...libre.com, kuznet@....inr.ac.ru,
linux-amlogic@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
mark.rutland@....com, netdev@...r.kernel.org, robh+dt@...nel.org,
syzkaller-bugs@...glegroups.com, yoshfuji@...ux-ipv6.org
Subject: Re: WARNING: bad unlock balance detected! (3)
On Sat, 2019-03-23 at 07:14 -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit ec01fb69ac8034ad6e839b31f9df167a110f868b
> Author: Jerome Brunet <jbrunet@...libre.com>
> Date: Wed Jan 16 17:59:47 2019 +0000
>
> arm64: dts: meson: s400: fix emmc maximum rate
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10afb7cf200000
> start commit: 065b6c4c Merge tag 'devicetree-for-5.1' of git://git.kerne..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=12afb7cf200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=14afb7cf200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ea4067c9a08ae046
> dashboard link: https://syzkaller.appspot.com/bug?extid=f3e3434787332dfc1c47
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a10577200000
>
> Reported-by: syzbot+f3e3434787332dfc1c47@...kaller.appspotmail.com
> Fixes: ec01fb69ac80 ("arm64: dts: meson: s400: fix emmc maximum rate")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Hi David,
I'm not sure I understand what the problem reported is but I don't think a DT
patch could be the cause of a locking issue on x86.
If I missed something, feel free to let me know.
Cheers
Jerome
Powered by blists - more mailing lists