netdev - Re: [PATCH V2 net-next 1/1] hyperv: Properly handle checksum offload

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:	Wed, 30 Apr 2014 13:34:10 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	kys@...rosoft.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
	jasowang@...hat.com, stable@...nel.org
Subject: Re: [PATCH V2 net-next 1/1] hyperv: Properly handle checksum
 offload

From: "K. Y. Srinivasan" <kys@...rosoft.com>
Date: Wed, 30 Apr 2014 09:05:21 -0700

> Do checksum offload only if the client of the driver wants checksum to be
> offloaded.
> 
> In V1 version of this patch, I  addressed comments from
> Stephen Hemminger <stephen@...workplumber.org> and
> Eric Dumazet <eric.dumazet@...il.com>.
> 
> In this version of the patch I have addressed comments from
> David Miller.
> 
> This patch fixes a bug that is exposed in gateway scenarios.
> 
> 
> Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> Reviewed-by: Haiyang Zhang <haiyangz@...rosoft.com>

It does not make any sense to submit a patch for net-next and
also ask for it to be included in -stable.

First of all, -stable submissions are handled by me directly for
networking.  Therefore you should not CC: stable on such patches,
instead you ask me politly to include it in my stable submission
queue.

Second of all, if a patch is destined for stable, it should be
submitted for 'net' not 'net-next'.
--
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