[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200124124512.GT29276@dhcp22.suse.cz>
Date: Fri, 24 Jan 2020 13:45:12 +0100
From: Michal Hocko <mhocko@...nel.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: David Hildenbrand <david@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
stable <stable@...r.kernel.org>,
Vishal Verma <vishal.l.verma@...el.com>,
Pavel Tatashin <pasha.tatashin@...een.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Linux MM <linux-mm@...ck.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/memory_hotplug: Fix remove_memory() lockdep splat
On Fri 10-01-20 13:27:24, Dan Williams wrote:
> On Fri, Jan 10, 2020 at 9:42 AM David Hildenbrand <david@...hat.com> wrote:
[...]
> > For your reference (roughly 5 months ago, so not that old)
> >
> > https://lkml.kernel.org/r/20190724143017.12841-1-david@redhat.com
>
> Oh, now I see the problem. You need to add that lock so far away from
> the __add_memory() to avoid lock inversion problems with the
> acpi_scan_lock. The organization I was envisioning would not work
> without deeper refactoring.
Sorry to come back to this late. Has this been resolved?
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists