netdev - Re: [PATCH] bridge: reset IPCB in br_parse_ip

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: <20110413082457.52784d6d@nehalam>
Date:	Wed, 13 Apr 2011 08:24:57 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Scot Doyle <lkml@...tdoyle.com>
Cc:	Eric Dumazet <eric.dumazet@...il.com>,
	David Miller <davem@...emloft.net>,
	Hiroaki SHIMODA <shimoda.hiroaki@...il.com>,
	netdev@...r.kernel.org
Subject: Re: [PATCH] bridge: reset IPCB in br_parse_ip_options


> The net effect is that three patches are required to eliminate the panics.
> 
> These two patches have been accepted by David:
> http://article.gmane.org/gmane.linux.network/192015
> http://article.gmane.org/gmane.linux.network/192055
> 
> This patch, incrementally authored by Stephen and Eric and compiled by 
> me, is also required:
> http://article.gmane.org/gmane.linux.network/192007
> 
> What should happen for this third patch to be included upstream?

Although making IP more robust is a good.
I still think bridging shouldn't give bad packets to IP.
--
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