linux-kernel - Re: [sched/core] 8a8c69c327: WARNING: CPU: 0 PID: 8 at kernel/locking/lockdep.c:3548 lock

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]

Date:   Fri, 17 Mar 2017 15:13:35 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Wanpeng Li <kernellwp@...il.com>
Cc:     kernel test robot <fengguang.wu@...el.com>, LKP <lkp@...org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>, wfg@...ux.intel.com
Subject: Re: [sched/core] 8a8c69c327: WARNING: CPU: 0 PID: 8 at
 kernel/locking/lockdep.c:3548 lock_release

On Fri, Mar 17, 2017 at 03:09:09PM +0100, Peter Zijlstra wrote:
> On Fri, Mar 17, 2017 at 09:24:11PM +0800, Wanpeng Li wrote:
> > I have another version of patch which utilizes raw_spin_lock_irqsave()
> > instead of rq_lock_irqsave() in __balance_callback() as before, which
> > one do you like, Peterz?
> 
> Hurm.. the raw_spin_lock_irqsave() one I suspect. No point in pinning
> and then unpinning.

Took your other version and edited that to make it do this.