linux-kernel - Re: linux-next boot error: BUG: Invalid wait context ]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACT4Y+apEBx58B7q7XOMrPzzXZiQ6zvnVLRypD1MxCURwNkkMg@mail.gmail.com>
Date:   Wed, 20 May 2020 15:41:45 +0200
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     syzbot <syzbot+08003d278f04ed0944e0@...kaller.appspotmail.com>,
        Frédéric Weisbecker <fweisbec@...il.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: linux-next boot error: BUG: Invalid wait context ]

On Wed, May 20, 2020 at 2:04 PM Thomas Gleixner <tglx@...utronix.de> wrote:
>
> syzbot <syzbot+08003d278f04ed0944e0@...kaller.appspotmail.com> writes:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:    fb57b1fa Add linux-next specific files for 20200519
> > git tree:       linux-next
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17c9196e100000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=2522f758a3588c2d
> > dashboard link: https://syzkaller.appspot.com/bug?extid=08003d278f04ed0944e0
> > compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+08003d278f04ed0944e0@...kaller.appspotmail.com
> >
> > =============================
> > [ BUG: Invalid wait context ]
> > 5.7.0-rc6-next-20200519-syzkaller #0 Not tainted
> > -----------------------------
> > swapper/1/0 is trying to lock:
> > ffff8880ae737518 (&pool->lock){..-.}-{3:3}, at: spin_lock include/linux/spinlock.h:353 [inline]
> > ffff8880ae737518 (&pool->lock){..-.}-{3:3}, at: __queue_work+0x2bf/0x1350 kernel/workqueue.c:1448
>
> Can you please disable CONFIG_PROVE_RAW_LOCK_NESTING for now?
>
> From the help text:
>
> NOTE:
>   There are known nesting problems. So if you enable this option expect
>   lockdep splats until these problems have been fully addressed which is
>   work in progress. This config switch allows to identify and analyze
>   these problems. It will be removed and the check permanentely enabled
>   once the main issues have been fixed.

Hi Thomas,

Done:
https://github.com/google/syzkaller/commit/4afdfa205b55633e7eb9db03a9d099d7aa324801

We can obsolete this then:

#syz invalid