Thanks!
On Wed, Sep 09, 2020 at 06:19:06AM -0700, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit f08e3888574d490b31481eef6d84c61bedba7a47
> Author: Boqun Feng
> Date: Fri Aug 7 07:42:30 2020 +
>
> lockdep: Fix recursive read lock related safe->unsafe detection
>
>
syzbot has bisected this issue to:
commit f08e3888574d490b31481eef6d84c61bedba7a47
Author: Boqun Feng
Date: Fri Aug 7 07:42:30 2020 +
lockdep: Fix recursive read lock related safe->unsafe detection
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13034be190
start
] type 2 family 0 port 6081 - 0
=
WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
5.9.0-rc4-next-20200908-syzkaller #0 Not tainted
-
syz-executor198/6886 [HC0[0]:SC0[0]:HE0:
OK. Patch was sent to linux.git as 6c1e851c4edc13a4.
#syz fix: random: fix possible sleeping allocation from irq context
OK. Patch was sent to linux.git as 6c1e851c4edc13a4.
#syz fix: random: fix possible sleeping allocation from irq context
On Mon, Apr 23, 2018 at 10:49:12AM -0700, Dmitry Torokhov wrote:
> On Sun, Apr 22, 2018 at 7:02 PM, syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot hit the following crash on upstream commit
> > 285848b0f4074f04ab606f1e5dca296482033d54 (Sun Apr
On Mon, Apr 23, 2018 at 10:49:12AM -0700, Dmitry Torokhov wrote:
> On Sun, Apr 22, 2018 at 7:02 PM, syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot hit the following crash on upstream commit
> > 285848b0f4074f04ab606f1e5dca296482033d54 (Sun Apr 22 04:20:48 2018 +)
> > Merge tag
by: syzbot+e1670f554caa60fb1...@syzkaller.appspotmail.com
> It will help syzbot understand when the bug is fixed. See footer for details.
> If you forward the report, please keep this part and the footer.
>
>
> ===
ter for details.
> If you forward the report, please keep this part and the footer.
>
>
> =====
> WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
> 4.17.0-rc1+ #12 Not tainted
> --
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
=
WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
4.17.0-rc1+ #12 Not tain
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
=
WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
4.17.0-rc1+ #12 Not tain
11 matches
Mail list logo