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]
Date:   Thu, 6 Sep 2018 08:37:00 +0800
From:   Rong Chen <rong.a.chen@...el.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Linux Memory Management List <linux-mm@...ck.org>,
        Andrew Morton <akpm@...ux-foundation.org>, LKP <lkp@...org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [LKP] 3f906ba236 [ 71.192813] WARNING: possible circular locking
 dependency detected



On 09/05/2018 09:02 PM, Thomas Gleixner wrote:
> On Wed, 5 Sep 2018, kernel test robot wrote:
>
>> Greetings,
>>
>> 0day kernel testing robot got the below dmesg and the first bad commit is
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>
>> commit 3f906ba23689a3f824424c50f3ae937c2c70f676
>> Author:     Thomas Gleixner <tglx@...utronix.de>
>> AuthorDate: Mon Jul 10 15:50:09 2017 -0700
>> Commit:     Linus Torvalds <torvalds@...ux-foundation.org>
>> CommitDate: Mon Jul 10 16:32:33 2017 -0700
> So it identified a more than one year old commit. Great.
>
>> vm86 returned ENOSYS, marking as inactive. 20044 iterations. [F:14867 S:5032 HI:3700] [ 57.651003] synth uevent: /module/pcmcia_core: unknown uevent action string [ 71.189062] [ 71.191953] ====================================================== [ 71.192813] WARNING: possible circular locking dependency detected [ 71.193664] 4.12.0-10480-g3f906ba #1 Not tainted [ 71.194355] ------------------------------------------------------ [ 71.195211] trinity-c0/1666 is trying to acquire lock: [ 71.195958] (mem_hotplug_lock.rw_sem){.+.+.+}, at: show_slab_objects+0x14b/0x440 [ 71.197284] [ 71.197284] but task is already holding lock:
> along with completely unparseable information. What am I supposed to do
> with this mail?
Hi,

Attached please find the dmesg/reproduce files in previous mail.
please ignore the report if it's a false positive.

Best Regards,
Rong Chen

>
> Thanks,
>
> 	tglx
> _______________________________________________
> LKP mailing list
> LKP@...ts.01.org
> https://lists.01.org/mailman/listinfo/lkp

Powered by blists - more mailing lists