netdev - Re: [stable] [PATCH 2.6.36 stable] vlan: Avoid hwaccel vlan packets when vid not used.

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: <1291755026.5324.3.camel@edumazet-laptop>
Date:	Tue, 07 Dec 2010 21:50:26 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Greg KH <greg@...ah.com>
Cc:	Jesse Gross <jesse@...ira.com>, stable@...nel.org,
	netdev@...r.kernel.org, David Miller <davem@...emloft.net>
Subject: Re: [stable] [PATCH 2.6.36 stable] vlan: Avoid hwaccel vlan
 packets when vid not used.

Le mardi 07 décembre 2010 à 11:50 -0800, Greg KH a écrit :
> On Mon, Nov 08, 2010 at 01:23:01PM -0800, Jesse Gross wrote:
> > Normally hardware accelerated vlan packets are quickly dropped if
> > there is no corresponding vlan device configured.  The one exception
> > is promiscuous mode, where we allow all of these packets through so
> > they can be picked up by tcpdump.  However, this behavior causes a
> > crash if we actually try to receive these packets.  This fixes that
> > crash by ignoring packets with vids not corresponding to a configured
> > device in the vlan hwaccel routines and then dropping them before they
> > get to consumers in the network stack.
> > 
> > This patch applies only to 2.6.36 stable.  The problem was introduced
> > in that release and is already fixed by larger changes to the vlan
> > code in 2.6.37.
> 
> Applied, thanks.
> 

Oh well, which version ?

A new version of the patch was submitted 6 days ago .

http://patchwork.ozlabs.org/patch/73791/

Thanks




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