linux-kernel - Re: 2.6.31 regression: e1000e jumbo frames no longer work: 'Unsupported MTU setting'

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: <87ab0elrnd.fsf@spindle.srvr.nix>
Date:	Mon, 28 Sep 2009 21:51:18 +0100
From:	Nix <nix@...eri.org.uk>
To:	Alexander Duyck <alexander.duyck@...il.com>
Cc:	e1000-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	netdev <netdev@...r.kernel.org>, bruce.w.allan@...el.com
Subject: Re: 2.6.31 regression: e1000e jumbo frames no longer work:  'Unsupported MTU setting'

On 27 Sep 2009, Alexander Duyck said:
> It looks like the problem is that the 82574 and 82583 seem to have
> their max_hw_frame_size values swapped.  You might try applying the
> patch below.  I am not sure if it will apply since I hand generated it

Applies fine: works fine. Thank you!

> using the git patch that seems to have introduced the problem, and I
> am sending the patch through an untested account that may mangle the
> patch.

Unmangled.

>        I will see about submitting an official patch for this
> sometime next few days.

I wonder if this belongs in -stable? People with an 82574 who are using
jumbo frames may well find their networks not coming up, if like me
they set a bunch of properties in one /sbin/ip call.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/