From: Andrew Morton <akpm@linux-foundation.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: KY Srinivasan <kys@microsoft.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
Tang Chen <tangchen@cn.fujitsu.com>,
Vlastimil Babka <vbabka@suse.cz>,
David Rientjes <rientjes@google.com>,
Fabian Frederick <fabf@skynet.be>,
Zhang Zhen <zhenzhang.zhang@huawei.com>,
Vladimir Davydov <vdavydov@parallels.com>,
Wang Nan <wangnan0@huawei.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH RESEND 0/3] memory_hotplug: hyperv: fix deadlock between memory adding and onlining
Date: Thu, 12 Feb 2015 14:25:06 -0800 [thread overview]
Message-ID: <20150212142506.09b427a9128a3a3b1ded36a4@linux-foundation.org> (raw)
In-Reply-To: <4323296.ObXCUgVR2I@vostro.rjw.lan>
On Thu, 12 Feb 2015 23:43:17 +0100 "Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:
> On Thursday, February 12, 2015 10:10:30 PM KY Srinivasan wrote:
>
> [cut]
yay!
> > > > > >
> > > > > > This issue was first discovered by Andy Whitcroft:
> > > > > > https://lkml.org/lkml/2014/3/14/451
> > > > > > I had sent patches based on Andy's analysis that did not affect
> > > > > > the users of the kernel hot-add memory APIs:
> > > > > > https://lkml.org/lkml/2014/12/2/662
> > > > > >
> > > > > > This patch puts the burden where it needs to be and can address
> > > > > > the issue
> > > > > for all clients.
> > > > >
> > > > > That seems to mean that this series is not needed. Is that correct?
> > > >
> > > > This patch was never committed upstream and so the issue still is there.
> > >
> > > Well, I'm not sure what to do now to be honest.
> > >
> > > Is this series regarded as the right way to address the problem that
> > > everybody is comfortable with? Or is it still under discussion?
> >
> > We need to solve this problem and that is not under discussion. I also believe this problem
> > needs to be solved in a way that addresses the problem where it belongs - not in the users of
> > the hot_add API. Both my solution and the one proposed by David https://lkml.org/lkml/2015/2/12/57
> > address this issue. You can select either patch and check it in. I just want the issue addressed and I am not
> > married to the solution I proposed.
>
> OK, thanks!
>
> So having looked at both your patch and the David's one I think that
> the Andrew's tree is appropriate for any of them.
>
> Andrew?
OK, I'll wake up and take a look. Hopefully as 3.21 material but I
need to to back and reread everything. Is it more urgent than that?
--
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:[~2015-02-12 22:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 10:23 Vitaly Kuznetsov
2015-02-12 10:23 ` [PATCH RESEND 1/3] driver core: export lock_device_hotplug/unlock_device_hotplug Vitaly Kuznetsov
2015-02-12 10:23 ` [PATCH RESEND 2/3] memory_hotplug: add note about holding device_hotplug_lock and add_memory() Vitaly Kuznetsov
2015-02-12 10:23 ` [PATCH RESEND 3/3] Drivers: hv: balloon: fix deadlock between memory adding and onlining Vitaly Kuznetsov
2015-02-12 15:38 ` [PATCH RESEND 0/3] memory_hotplug: hyperv: " KY Srinivasan
2015-02-12 15:50 ` Vitaly Kuznetsov
2015-02-12 17:40 ` KY Srinivasan
2015-02-12 22:12 ` Rafael J. Wysocki
2015-02-12 22:01 ` KY Srinivasan
2015-02-12 22:27 ` Rafael J. Wysocki
2015-02-12 22:10 ` KY Srinivasan
2015-02-12 22:43 ` Rafael J. Wysocki
2015-02-12 22:25 ` Andrew Morton [this message]
2015-03-06 15:50 ` Michal Hocko
2015-03-09 8:40 ` Vitaly Kuznetsov
2015-03-12 16:18 ` Michal Hocko
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=20150212142506.09b427a9128a3a3b1ded36a4@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=fabf@skynet.be \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=rjw@rjwysocki.net \
--cc=tangchen@cn.fujitsu.com \
--cc=vbabka@suse.cz \
--cc=vdavydov@parallels.com \
--cc=vkuznets@redhat.com \
--cc=wangnan0@huawei.com \
--cc=zhenzhang.zhang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox