linux-kernel - Re: [PATCH v8 05/14] lockdep: Implement crossrelease feature

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: <20170810092145.6avlhvepnneh3swm@hirez.programming.kicks-ass.net>
Date:   Thu, 10 Aug 2017 11:21:45 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Byungchul Park <byungchul.park@....com>
Cc:     mingo@...nel.org, tglx@...utronix.de, walken@...gle.com,
        boqun.feng@...il.com, kirill@...temov.name,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        akpm@...ux-foundation.org, willy@...radead.org, npiggin@...il.com,
        kernel-team@....com
Subject: Re: [PATCH v8 05/14] lockdep: Implement crossrelease feature

On Thu, Aug 10, 2017 at 10:30:54AM +0900, Byungchul Park wrote:

> With a little feedback, it rather makes us a bit confused between
> XHLOCK_NR and MAX_XHLOCK_NR. what about the following?
> 
> +enum xhlock_context_t {
> +       XHLOCK_HARD,
> +       XHLOCK_SOFT,
> +       XHLOCK_PROC,
> +       XHLOCK_CXT_NR,
> +};
> 
> But it's trivial. I like yours, too.

grep -l "XHLOCK_NR" `quilt series` | while read file; do sed -i
's/XHLOCK_NR/XHLOCK_CTX_NR/g' $file; done

:-)