linux-kernel - Re: [PATCH 1/1] drivers: hid: hid-hyperv: Properly disconnect the input device

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

Date:	Thu, 2 Feb 2012 10:56:37 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	"K. Y. Srinivasan" <kys@...rosoft.com>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, virtualization@...ts.osdl.org,
	ohering@...e.com, joe@...ches.com, dmitry.torokhov@...il.com,
	Haiyang Zhang <haiyangz@...rosoft.com>,
	stable <stable@...r.kernel.org>
Subject: Re: [PATCH 1/1] drivers: hid: hid-hyperv: Properly disconnect the
 input device

On Wed, 18 Jan 2012, K. Y. Srinivasan wrote:

> When we unload the mouse driver, properly disconnect the input device.
> 
> Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> Signed-off-by: Haiyang Zhang <haiyangz@...rosoft.com>
> Reported-by: Fuzhou Chen <fuzhouch@...rosoft.com>
> Cc: stable <stable@...r.kernel.org>
> ---
>  drivers/hid/hid-hyperv.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/hid/hid-hyperv.c b/drivers/hid/hid-hyperv.c
> index 0c33ae9..4066324 100644
> --- a/drivers/hid/hid-hyperv.c
> +++ b/drivers/hid/hid-hyperv.c
> @@ -548,6 +548,7 @@ static int mousevsc_remove(struct hv_device *dev)
>  	struct mousevsc_dev *input_dev = hv_get_drvdata(dev);
>  
>  	vmbus_close(dev->channel);
> +	hid_hw_stop(input_dev->hid_device);
>  	hid_destroy_device(input_dev->hid_device);
>  	mousevsc_free_device(input_dev);

Applied, thanks.

-- 
Jiri Kosina
SUSE Labs
--
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/