netdev - RE: hyperv: fix apparent cut-n-paste error in send path teardown

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]

Message-ID: <1c8d2b180c6c45e09f41282904ebdb1c@BY2PR03MB299.namprd03.prod.outlook.com>
Date:	Tue, 17 Jun 2014 10:13:25 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Dave Jones <davej@...hat.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: hyperv: fix apparent cut-n-paste error in send path teardown



> -----Original Message-----
> From: Dave Jones [mailto:davej@...hat.com]
> Sent: Monday, June 16, 2014 1:59 PM
> To: netdev@...r.kernel.org
> Cc: KY Srinivasan
> Subject: hyperv: fix apparent cut-n-paste error in send path teardown
> 
> c25aaf814a63: "hyperv: Enable sendbuf mechanism on the send path" added
> some teardown code that looks like it was copied from the recieve path
> above, but missed a variable name replacement.

Thank you.

K. Y
> 
> Signed-off-by: Dave Jones <davej@...hat.com>
> 
> diff --git a/drivers/net/hyperv/netvsc.c b/drivers/net/hyperv/netvsc.c index
> c041f63a6d30..4ed38eaecea8 100644
> --- a/drivers/net/hyperv/netvsc.c
> +++ b/drivers/net/hyperv/netvsc.c
> @@ -189,7 +189,7 @@ static int netvsc_destroy_buf(struct netvsc_device
> *net_device)
>  				   "unable to teardown send buffer's
> gpadl\n");
>  			return ret;
>  		}
> -		net_device->recv_buf_gpadl_handle = 0;
> +		net_device->send_buf_gpadl_handle = 0;
>  	}
>  	if (net_device->send_buf) {
>  		/* Free up the receive buffer */
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html