linux-kernel - Re: [PATCH net-next] xen-netback: Fix pull size in checksum_setup

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: <20131130.161000.1050565138363035368.davem@davemloft.net>
Date:	Sat, 30 Nov 2013 16:10:00 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	zoltan.kiss@...rix.com
Cc:	ian.campbell@...rix.com, wei.liu2@...rix.com,
	xen-devel@...ts.xenproject.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, jonathan.davies@...rix.com,
	paul.durrant@...rix.com
Subject: Re: [PATCH net-next] xen-netback: Fix pull size in
 checksum_setup_ip*

From: Zoltan Kiss <zoltan.kiss@...rix.com>
Date: Fri, 29 Nov 2013 18:56:47 +0000

> Before checksum setup we need to make sure we have enough data in linear
> buffer, so we do a pull if not. The calculation of the required data counts
> with skb->network_header, which is the headroom size actually. This is not
> necessary, and can cause unreasonable pulling. I've also removed
> MAX_IPOPTLEN, as we only need the base header at that point.
> 
> Signed-off-by: Zoltan Kiss <zoltan.kiss@...rix.com>

The net-next tree is no open, therefore it is not appropriate to submit
patches targetting to that tree at this time.

I will make an explicit announcement on netdev when I have openned
the net-next tree, so it will be clear exactly when you can submit
patches targetting that tree again.

Thank you.
--
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/