Re: WARNING: bad unlock balance detected! (3)

From: Jerome Brunet
Date: Mon Mar 25 2019 - 07:54:59 EST


On Sat, 2019-03-23 at 07:14 -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit ec01fb69ac8034ad6e839b31f9df167a110f868b
> Author: Jerome Brunet <jbrunet@xxxxxxxxxxxx>
> 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@xxxxxxxxxxxxxxxxxxxxxxxxx
> 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