netdev - Re: e1000 vlan functionality broken in 3.1

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] [day] [month] [year] [list]

Message-ID: <20111121220509.GA2444@minipsycho>
Date:	Mon, 21 Nov 2011 23:05:10 +0100
From:	Jiri Pirko <jpirko@...hat.com>
To:	Josh Boyer <jwboyer@...hat.com>
Cc:	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	kernel-team@...oraproject.org
Subject: Re: e1000 vlan functionality broken in 3.1

Mon, Nov 21, 2011 at 08:28:39PM CET, jwboyer@...hat.com wrote:
>Hi All,
>
>We've had a couple of reports of the e1000 driver no longer working with
>tagged VLANs in the 3.1 kernel.  The bug report has much more detail
>here:
>
>https://bugzilla.redhat.com/show_bug.cgi?id=754589
>
>The summary is, if you turn of rxvlan and tx offloading, the driver
>seems to work fine with 3.1 again whereas this wasn't needed on 3.0.
>(Fedora calls 3.0 2.6.40 on Fedora 15, but that is strictly a naming
>thing.)
>
>Looking through the commit logs, 5622e4044a91 seems to be the most
>relevant commit between those versions.  Does anyone have any ideas?


Looking at the patch again, I do not see anything suspicious. Plus the
bugzilla is talking about carrupting tx packets which is really odd. One
thing I can think of is if maybe VLAN tag inserting/striping and enable
VLAN receive filtering might be needed to be enabled/disabled together.
Intel guys should be able to tell.

Thanks.

Jirka

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