linux-kernel - Re: [PATCH v3] z3fold: use per-page read/write 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]

Message-ID: <20161109230117.GO26852@two.firstfloor.org>
Date:   Wed, 9 Nov 2016 15:01:17 -0800
From:   Andi Kleen <andi@...stfloor.org>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Vitaly Wool <vitalywool@...il.com>, Linux-MM <linux-mm@...ck.org>,
        linux-kernel@...r.kernel.org, Dan Streetman <ddstreet@...e.org>,
        Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH v3] z3fold: use per-page read/write lock

On Wed, Nov 09, 2016 at 02:33:04PM -0800, Andrew Morton wrote:
> On Wed, 9 Nov 2016 11:55:31 +0100 Vitaly Wool <vitalywool@...il.com> wrote:
> 
> > Subject: [PATCH v3] z3fold: use per-page read/write lock
> 
> I've rewritten the title to "mm/z3fold.c: use per-page spinlock"
> 
> (I prefer to have "mm" in the title to easily identify it as an MM
> patch, and using "mm: z3fold: ..." seems odd when the actual pathname
> conveys the same info.)

Still think it needs to be raw_spinlock_t, otherwise the build bug on
on the header size will break again. 

Better would be to fix that build bug though

-Andi