From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrey Ryabinin <aryabinin@virtuozzo.com>,
Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs. cpu hotplug lock
Date: Wed, 5 Jul 2017 14:53:34 -0700 [thread overview]
Message-ID: <20170705145334.d73a30dda944855349e522ed@linux-foundation.org> (raw)
In-Reply-To: <20170704093232.995040438@linutronix.de>
On Tue, 04 Jul 2017 11:32:32 +0200 Thomas Gleixner <tglx@linutronix.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?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrey Ryabinin <aryabinin@virtuozzo.com>,
Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs. cpu hotplug lock
Date: Wed, 5 Jul 2017 14:53:34 -0700 [thread overview]
Message-ID: <20170705145334.d73a30dda944855349e522ed@linux-foundation.org> (raw)
In-Reply-To: <20170704093232.995040438@linutronix.de>
On Tue, 04 Jul 2017 11:32:32 +0200 Thomas Gleixner <tglx@linutronix.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?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-07-05 21:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 9:32 [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs. cpu hotplug lock Thomas Gleixner
2017-07-04 9:32 ` Thomas Gleixner
2017-07-04 9:32 ` [patch V2 1/2] mm: swap: Provide lru_add_drain_all_cpuslocked() Thomas Gleixner
2017-07-04 9:32 ` Thomas Gleixner
2017-07-04 10:58 ` Michal Hocko
2017-07-04 10:58 ` Michal Hocko
2017-07-04 12:48 ` Thomas Gleixner
2017-07-04 12:48 ` Thomas Gleixner
2017-07-04 12:52 ` Michal Hocko
2017-07-04 12:52 ` Michal Hocko
2017-07-04 12:07 ` Vlastimil Babka
2017-07-04 12:07 ` Vlastimil Babka
2017-07-04 12:35 ` Thomas Gleixner
2017-07-04 12:35 ` Thomas Gleixner
2017-07-04 9:32 ` [patch V2 2/2] mm/memory-hotplug: Switch locking to a percpu rwsem Thomas Gleixner
2017-07-04 9:32 ` Thomas Gleixner
2017-07-04 10:59 ` Michal Hocko
2017-07-04 10:59 ` Michal Hocko
2017-07-04 12:10 ` Vlastimil Babka
2017-07-04 12:10 ` Vlastimil Babka
2017-07-04 12:49 ` Thomas Gleixner
2017-07-04 12:49 ` Thomas Gleixner
2017-07-04 15:01 ` Davidlohr Bueso
2017-07-04 15:01 ` Davidlohr Bueso
2017-07-04 15:22 ` Davidlohr Bueso
2017-07-04 15:22 ` Davidlohr Bueso
2017-07-04 15:32 ` Thomas Gleixner
2017-07-04 15:32 ` Thomas Gleixner
2017-07-04 15:42 ` Davidlohr Bueso
2017-07-04 15:42 ` Davidlohr Bueso
2017-07-05 21:53 ` Andrew Morton [this message]
2017-07-05 21:53 ` [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs. cpu hotplug lock Andrew Morton
2017-07-06 6:34 ` Thomas Gleixner
2017-07-06 6:34 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170705145334.d73a30dda944855349e522ed@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.