From: Jerome Brunet <jbrunet@baylibre.com>
To: syzbot <syzbot+f3e3434787332dfc1c47@syzkaller.appspotmail.com>,
davem@davemloft.net, devicetree@vger.kernel.org,
khilman@baylibre.com, kuznet@ms2.inr.ac.ru,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
netdev@vger.kernel.org, robh+dt@kernel.org,
syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org
Subject: Re: WARNING: bad unlock balance detected! (3)
Date: Mon, 25 Mar 2019 12:54:49 +0100 [thread overview]
Message-ID: <e3d9d95fd07502cccf8ef97ba7b2e2adb4eefbb3.camel@baylibre.com> (raw)
In-Reply-To: <0000000000003749360584c395ba@google.com>
On Sat, 2019-03-23 at 07:14 -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit ec01fb69ac8034ad6e839b31f9df167a110f868b
> Author: Jerome Brunet <jbrunet@baylibre.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@syzkaller.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
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet@baylibre.com>
To: syzbot <syzbot+f3e3434787332dfc1c47@syzkaller.appspotmail.com>,
davem@davemloft.net, devicetree@vger.kernel.org,
khilman@baylibre.com, kuznet@ms2.inr.ac.ru,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
netdev@vger.kernel.org, robh+dt@kernel.org,
syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org
Subject: Re: WARNING: bad unlock balance detected! (3)
Date: Mon, 25 Mar 2019 12:54:49 +0100 [thread overview]
Message-ID: <e3d9d95fd07502cccf8ef97ba7b2e2adb4eefbb3.camel@baylibre.com> (raw)
In-Reply-To: <0000000000003749360584c395ba@google.com>
On Sat, 2019-03-23 at 07:14 -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit ec01fb69ac8034ad6e839b31f9df167a110f868b
> Author: Jerome Brunet <jbrunet@baylibre.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@syzkaller.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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet@baylibre.com>
To: syzbot <syzbot+f3e3434787332dfc1c47@syzkaller.appspotmail.com>,
davem@davemloft.net, devicetree@vger.kernel.org,
khilman@baylibre.com, kuznet@ms2.inr.ac.ru,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
netdev@vger.kernel.org, robh+dt@kernel.org,
syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org
Subject: Re: WARNING: bad unlock balance detected! (3)
Date: Mon, 25 Mar 2019 12:54:49 +0100 [thread overview]
Message-ID: <e3d9d95fd07502cccf8ef97ba7b2e2adb4eefbb3.camel@baylibre.com> (raw)
In-Reply-To: <0000000000003749360584c395ba@google.com>
On Sat, 2019-03-23 at 07:14 -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit ec01fb69ac8034ad6e839b31f9df167a110f868b
> Author: Jerome Brunet <jbrunet@baylibre.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@syzkaller.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
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-03-25 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 7:10 WARNING: bad unlock balance detected! (3) syzbot
2019-03-23 14:14 ` syzbot
2019-03-23 14:14 ` syzbot
2019-03-23 14:14 ` syzbot
2019-03-25 11:54 ` Jerome Brunet [this message]
2019-03-25 11:54 ` Jerome Brunet
2019-03-25 11:54 ` Jerome Brunet
2019-03-26 8:30 ` Dmitry Vyukov
2019-03-26 8:30 ` Dmitry Vyukov
2019-03-26 8:30 ` Dmitry Vyukov
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=e3d9d95fd07502cccf8ef97ba7b2e2adb4eefbb3.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=syzbot+f3e3434787332dfc1c47@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.