From: David Miller <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
Date: Fri, 02 Apr 2010 14:36:27 -0700 (PDT) [thread overview]
Message-ID: <20100402.143627.11964909.davem@davemloft.net> (raw)
In-Reply-To: <87iq89q3v2.fsf@spindle.srvr.nix>
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.
next prev parent reply other threads:[~2010-04-02 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 15:19 Nix
2010-04-02 21:36 ` David Miller [this message]
2010-04-02 22:03 ` Nix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100402.143627.11964909.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=nix@esperi.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome