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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200820123859.GS2674@hirez.programming.kicks-ass.net>
Date:   Thu, 20 Aug 2020 14:38:59 +0200
From:   peterz@...radead.org
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:     linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
        Will Deacon <will@...nel.org>, tglx@...utronix.de,
        kent.overstreet@...il.com
Subject: Re: [PATCH] lockdep: Do no validate wait context for novalidate class

On Thu, Aug 20, 2020 at 01:43:48PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-08-20 13:40:36 [+0200], peterz@...radead.org wrote:
> > Anyway, all 3 users should have the same wait context, so where is the
> > actual problem?
> 
> I have one in RT which is a per-CPU spinlock within local_bh_disable()
> to act as a per-CPU BLK like mainline.

Then can we get to see that code and an explanation for what the problem
is and why it is still correct?

Because as is, this patch isn't needed.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ