netdev - Re: [PATCHv2 net 0/3] Prevent extreme TSO parameters from stalling TX queues

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20120802.002045.2029236086125448605.davem@davemloft.net>
Date:	Thu, 02 Aug 2012 00:20:45 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	bhutchings@...arflare.com
Cc:	netdev@...r.kernel.org, linux-net-drivers@...arflare.com,
	greearb@...delatech.com, eric.dumazet@...il.com,
	shemminger@...tta.com
Subject: Re: [PATCHv2 net 0/3] Prevent extreme TSO parameters from stalling
 TX queues

From: Ben Hutchings <bhutchings@...arflare.com>
Date: Tue, 31 Jul 2012 02:51:16 +0100

> The following changes fix a potential DoS by peers or local users on
> network interfaces using the sfc driver (and possibly others) with TSO
> enabled (as it is by default).
> 
> Please apply patches 1 and 2 to the net tree and your stable update
> queue.  I'm not sure whether patch 3 is really important.
> 
> Ben.
> 
> Ben Hutchings (3):
>   net: Allow driver to limit number of GSO segments per skb
>   sfc: Fix maximum number of TSO segments and minimum TX queue size
>   tcp: Apply device TSO segment limit earlier

Series applied, thanks Ben.  I think patch #3 does matter, because
anything in TCP that cares about the "limit" now must make both
tests.

--
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