linux-kernel - Re: [perf_event_ctx_lock_nested] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:97

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171030085210.eyoaxwg72w4ovqqf@wfg-t540p.sh.intel.com>
Date:   Mon, 30 Oct 2017 09:52:10 +0100
From:   Fengguang Wu <fengguang.wu@...el.com>
To:     Peter Zijlstra <peterz@...radead.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        lkp@...el.com
Subject: Re: [perf_event_ctx_lock_nested] BUG: sleeping function called from
 invalid context at kernel/locking/mutex.c:97

On Mon, Oct 30, 2017 at 09:42:25AM +0100, Peter Zijlstra wrote:
>On Mon, Oct 30, 2017 at 12:02:01AM +0100, Fengguang Wu wrote:
>> The dmesg fragment is
>>
>> [   40.886662] done
>> [   40.886686] [   40.905102] capability: warning: `turbostat' uses 32-bit
>> capabilities (legacy support in use)
>> [   40.940087] IPMI Device Information
>> [   41.073351] [   41.076223] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:97
>> [   41.076224] in_atomic(): 1, irqs_disabled(): 0, pid: 14, name: watchdog/0
>> [   41.076226] CPU: 0 PID: 14 Comm: watchdog/0 Tainted: G           O    4.8.0-01558-g21f54dd #1
>                                                                           ^^^^^^^^^^^^^^^^^^^^
>
>That's not 4.14 or even close.

Yeah sorry -- it looks like a 0day bug. So the robot stores dmesg
files to the wrong commit dir, which made me believe they are all RC6
bugs. Sorry for the noises! 

Regards,
Fengguang