From: Michael Tokarev <mjt@tls.msk.ru>
To: netdev <netdev@vger.kernel.org>
Subject: r8169: instant crash if receiving packet larger than MTU
Date: Sat, 14 Feb 2009 18:16:36 +0300 [thread overview]
Message-ID: <4996E054.20905@msgid.tls.msk.ru> (raw)
I played with jumbo frames today at home on two
machines with built-in r8169 NICs. And discovered
that, after enabling larger packets on one machine,
it's sufficient to send SINGLE packet to immediately,
instantly crash the other machine.
I'd say it's quite a serious issue. Good it usually
can't be triggered "from outside" (from the Internet)
because there, standard 1500-sized MTU is usually
used (or at least in last-mile network segment), but
on LAN it's quite common nowadays to at least HAVE
the jumbo-capable equipment, and that's all what's
needed to trigger this.
Comments?
(The system in question is based on an Asus M3A78-EM
motherboard, here's the lspci info for the NIC:
02:00.0 0200: 10ec:8168 (rev 02)
Subsystem: 1043:82c6
Flags: bus master, fast devsel, latency 0, IRQ 509
I/O ports at e800 [size=256]
Memory at fbeff000 (64-bit, non-prefetchable) [size=4K]
Memory at faff0000 (64-bit, prefetchable) [size=64K]
Expansion ROM at fbec0000 [disabled] [size=128K]
Capabilities: [40] Power Management version 3
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Mask- TabSize=2
Capabilities: [d0] Vital Product Data <?>
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Capabilities: [160] Device Serial Number 81-68-10-ec-00-00-00-00
Kernel driver in use: r8169
Kernel modules: r8169
)
Thanks!
/mjt
next reply other threads:[~2009-02-14 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 15:16 Michael Tokarev [this message]
2009-02-17 19:37 ` r8169: instant crash if receiving packet larger than MTU Francois Romieu
2009-02-17 20:55 ` Michael Tokarev
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=4996E054.20905@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).