linux-kernel - Re: [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches

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]

Message-ID: <a5d28322-fe37-fc88-6127-2f8abba81afe@redhat.com>
Date:   Thu, 18 Apr 2019 08:42:42 -0400
From:   Waiman Long <longman@...hat.com>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Will Deacon <will.deacon@....com>,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-kernel@...r.kernel.org, x86@...nel.org,
        Davidlohr Bueso <dave@...olabs.net>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Tim Chen <tim.c.chen@...ux.intel.com>,
        huang ying <huang.ying.caritas@...il.com>
Subject: Re: [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2
 follow-up patches

On 04/18/2019 04:02 AM, Ingo Molnar wrote:
> * Waiman Long <longman@...hat.com> wrote:
>
>> As the part2 patches are still being actively modified, it doesn't look 
>> like it will make the next merge window. I am fine with postponing it 
>> to 5.3. However, I would like to request the merging of just patch 1 of 
>> the part 2 patchset. It fixes a locking selftest problem that was 
>> introduced in the part 1 patches.
> Sure, I've promoted this commit:
>
>   26536e7c242e: locking/rwsem: Prevent unneeded warning during locking selftest
>
> from tip:WIP.locking/core into tip:locking/core, for a v5.2 merge.
>
> Thanks,
>
> 	Ingo

Thanks for the help. I just don't want to get report of known problem
during the next merge window.

Cheers,
Longman