netdev - Re: [PATCH 0/2] Disable forwarding of LRO skbs [2nd try]

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: <20080619145009.5b24f028@extreme>
Date:	Thu, 19 Jun 2008 14:50:09 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-net-drivers@...arflare.com,
	Kieran Mansley <kmansley@...arflare.com>,
	Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [PATCH 0/2] Disable forwarding of LRO skbs [2nd try]

On Thu, 19 Jun 2008 19:44:56 +0100
Ben Hutchings <bhutchings@...arflare.com> wrote:

> [Re-sent with the correct Message-ID, previously eaten by mutt.]
> 
> Large Receive Offload (LRO) destroys packet headers that should be
> preserved when forwarding.  Currently it also triggers a BUG() or WARN()
> in skb_gso_segment().  We should disable it wherever forwarding is
> enabled, and discard LRO skbs with a warning if it is turned back on.
> 
> Since the previous version of these patches, I have:
> - Tightened the test for LRO'd skbs, so it should not catch skbs from
>   VM guests that want GSO
> - Made the test an inline function, with the warning a separate extern
>   function
> - Rebased against net-next-2.6
> 

I like that it covers both cases and looks clean. If anyone ever gets
around to rewriting the network device driver chapter in the linux
kernel book(s) this should be covered in more detail.
--
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