Date: Fri, 02 Apr 2010 14:36:27 -0700 (PDT)
Message-Id: <20100402.143627.11964909.davem@davemloft.net>
To: nix@esperi.org.uk
Cc: linux-kernel@vger.kernel.org, nhorman@redhat.com
Subject: Re: unhelpful and somewhat scary r8169 boot message in 2.6.33.2
 regarding a security fix
From: David Miller <davem@davemloft.net>
In-Reply-To: <87iq89q3v2.fsf@spindle.srvr.nix>
References: <87iq89q3v2.fsf@spindle.srvr.nix>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1177
Lines: 30

From: Nix <nix@esperi.org.uk>
Date: Fri, 02 Apr 2010 16:19:13 +0100

> So I was doing a test-boot of 2.6.33.2 to see if my hang-on-suspend
> Radeon DRM regression (fdo bug 26872) was cured (it wasn't), when a
> new message appeared at bootup, the second of those below:
> 
> [    8.766768] r8169: fastnet: link up
> [    8.791231] WARNING! Changing of MTU on this NICMay lead to frame reception errors!
> 
> (which appeared when I set the MTU on my r8169 to 7200.)
> 
> Not only is this message plainly misformatted :)

Formating has been fixed in the net-2.6 tree yesterday.

> but it does not explain *why* changing the MTU is suddenly so bad,
> when it's worked forever before now without flaw, with no sign of
> any sort of corruption. Why should we be confined to non-jumbo
> frames? What are the effects if we do change MTU?

Have a look at CVE-2009-4537

It's a remotely exploitable memory corruptor and potential
root hole.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/