From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: devel@linuxdriverproject.org,
Haiyang Zhang <haiyangz@microsoft.com>,
linux-kernel@vger.kernel.org, Dexuan Cui <decui@microsoft.com>
Subject: Re: [PATCH] Drivers: hv: hv_balloon: keep locks balanced on add_memory() failure
Date: Mon, 02 Mar 2015 11:33:41 +0100 [thread overview]
Message-ID: <87h9u3eliy.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1424435367-26384-1-git-send-email-vkuznets@redhat.com> (Vitaly Kuznetsov's message of "Fri, 20 Feb 2015 13:29:27 +0100")
Vitaly Kuznetsov <vkuznets@redhat.com> writes:
> When add_memory() fails the following BUG is observed:
> [ 743.646107] hv_balloon: hot_add memory failed error is -17
> [ 743.679973]
> [ 743.680930] =====================================
> [ 743.680930] [ BUG: bad unlock balance detected! ]
> [ 743.680930] 3.19.0-rc5_bug1131426+ #552 Not tainted
> [ 743.680930] -------------------------------------
> [ 743.680930] kworker/0:2/255 is trying to release lock (&dm_device.ha_region_mutex) at:
> [ 743.680930] [<ffffffff81aae5fe>] mutex_unlock+0xe/0x10
> [ 743.680930] but there are no more locks to release!
>
> This happens as we don't acquire ha_region_mutex and hot_add_req() expects us
> to as it does unconditional mutex_unlock(). Acquire the lock on the error path.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> ---
> This patch is dependent on the previously posted 'Drivers: hv: hv_balloon:
> eliminate the trylock path in acquire/release_region_mutex'.
Hi K.Y.,
I don't see this patch in your '[PATCH 0/7] Drivers: hv: Collection
fixes and enhancements' sent to Greg. Please let me know if you see any
issues with it as it looks like a pretty important bugfix to me.
Thanks,
> ---
> drivers/hv/hv_balloon.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hv/hv_balloon.c b/drivers/hv/hv_balloon.c
> index 1283035..771bf84 100644
> --- a/drivers/hv/hv_balloon.c
> +++ b/drivers/hv/hv_balloon.c
> @@ -654,6 +654,7 @@ static void hv_mem_hot_add(unsigned long start, unsigned long size,
> }
> has->ha_end_pfn -= HA_CHUNK;
> has->covered_end_pfn -= processed_pfn;
> + mutex_lock(&dm_device.ha_region_mutex);
> break;
> }
--
Vitaly
next prev parent reply other threads:[~2015-03-02 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 12:29 Vitaly Kuznetsov
2015-03-02 10:33 ` Vitaly Kuznetsov [this message]
2015-03-07 0:35 ` KY Srinivasan
2015-03-05 8:06 ` Jason Wang
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=87h9u3eliy.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome