linux-kernel - Re: [PATCH 07/10] drivers/hv: cleanup synic msrs if vmbus connect failed

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <5616A5A9.7020005@openvz.org>
Date:	Thu, 8 Oct 2015 20:19:37 +0300
From:	"Denis V. Lunev" <den@...nvz.org>
To:	"K. Y. Srinivasan" <kys@...rosoft.com>,
	<gregkh@...uxfoundation.org>, <linux-kernel@...r.kernel.org>,
	<devel@...uxdriverproject.org>, <olaf@...fle.de>,
	<apw@...onical.com>, <vkuznets@...hat.com>, <jasowang@...hat.com>
CC:	Andrey Smetanin <asmetanin@...tuozzo.com>,
	Haiyang Zhang <haiyangz@...rosoft.com>
Subject: Re: [PATCH 07/10] drivers/hv: cleanup synic msrs if vmbus connect
 failed

On 10/08/2015 05:01 AM, K. Y. Srinivasan wrote:
> From: Denis V. Lunev <den@...nvz.org>

K.Y.,

there is one subtle thing in this submission. You have changed "From:"
field in comparison with the original letter. I have submitted
the patch with "From: Andrey Smetanin <asmetanin@...tuozzo.com>"
In this case Author: in the resulted git mainstream commit will
be Andrey. With your submission the resulted Author will be I.

This was already happened once with

commit cc2dd4027a43bb36c846f195a764edabc0828602
Author: Denis V. Lunev <den@...nvz.org>
Date:   Sat Aug 1 16:08:20 2015 -0700

     mshyperv: fix recognition of Hyper-V guest crash MSR's

The situation looks a bit unfair.

Can we do something with that now/next time?

Den

> Before vmbus_connect() synic is setup per vcpu - this means
> hypervisor receives writes at synic msr's and probably allocate
> hypervisor resources per synic setup.
>
> If vmbus_connect() failed for some reason it's neccessary to cleanup
> synic setup by call hv_synic_cleanup() at each vcpu to get a chance
> to free allocated resources by hypervisor per synic.
>
> This patch does appropriate cleanup in case of vmbus_connect() failure.
>
> Signed-off-by: Andrey Smetanin <asmetanin@...tuozzo.com>
> Signed-off-by: Denis V. Lunev <den@...nvz.org>
> Reviewed-by: Vitaly Kuznetsov <vkuznets@...hat.com>
> CC: "K. Y. Srinivasan" <kys@...rosoft.com>
> CC: Haiyang Zhang <haiyangz@...rosoft.com>
> CC: Vitaly Kuznetsov <vkuznets@...hat.com>
> Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> ---
>   drivers/hv/vmbus_drv.c |    4 +++-
>   1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> index f19b6f7..3297731 100644
> --- a/drivers/hv/vmbus_drv.c
> +++ b/drivers/hv/vmbus_drv.c
> @@ -867,7 +867,7 @@ static int vmbus_bus_init(int irq)
>   	on_each_cpu(hv_synic_init, NULL, 1);
>   	ret = vmbus_connect();
>   	if (ret)
> -		goto err_alloc;
> +		goto err_connect;
>   
>   	if (vmbus_proto_version > VERSION_WIN7)
>   		cpu_hotplug_disable();
> @@ -885,6 +885,8 @@ static int vmbus_bus_init(int irq)
>   
>   	return 0;
>   
> +err_connect:
> +	on_each_cpu(hv_synic_cleanup, NULL, 1);
>   err_alloc:
>   	hv_synic_free();
>   	hv_remove_vmbus_irq();

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/