linux-kernel - Re: [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs. cpu hotplug 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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.20.1707060833130.1771@nanos>
Date:   Thu, 6 Jul 2017 08:34:00 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Andrew Morton <akpm@...ux-foundation.org>
cc:     LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
        Andrey Ryabinin <aryabinin@...tuozzo.com>,
        Michal Hocko <mhocko@...nel.org>,
        Vlastimil Babka <vbabka@...e.cz>,
        Vladimir Davydov <vdavydov.dev@...il.com>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs.
 cpu hotplug lock

On Wed, 5 Jul 2017, Andrew Morton wrote:
> On Tue, 04 Jul 2017 11:32:32 +0200 Thomas Gleixner <tglx@...utronix.de> wrote:
> 
> > Andrey reported a potential deadlock with the memory hotplug lock and the
> > cpu hotplug lock.
> > 
> > The following series addresses this by reworking the memory hotplug locking
> > and fixing up the potential deadlock scenarios.
> 
> Do you think we should squeeze this into 4.13-rc1, or can we afford to
> take the more cautious route?

The deadlocks are real and the lockdep splats are triggering on Linus head,
so it should go into 4.13-rc1 if possible.

Thanks,

	tglx