From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: netdev@vger.kernel.org
Subject: packet corruption or something else?
Date: Tue, 8 Jan 2008 14:49:18 +0200 [thread overview]
Message-ID: <20080108123414.M75319@visp.net.lb> (raw)
Hi
I notice a lot of messages like
[8447790.549705] UDP: short packet: From XXX.XXX.224.29:21005 60046/1480 to
XXX.XXX.247.1:1024
[8448040.893317] UDP: short packet: From XXX.XXX.224.29:21218 17820/1480 to
XXX.XXX.247.1:49974
[8448216.603759] UDP: short packet: From XXX.XXX.224.29:21004 56347/1480 to
XXX.XXX.247.1:1024
[8448370.883610] UDP: short packet: From XXX.XXX.224.29:21005 5246/1480 to
XXX.XXX.247.1:1251
I have similar messages on other hosts, and they looks very strange.
After looking to kernel sources i found
ulen = ntohs(uh->len);
if (ulen > skb->len)
goto short_packet;
if (proto == IPPROTO_UDP) {
/* UDP validates ulen. */
if (ulen < sizeof(*uh) || pskb_trim_rcsum(skb, ulen))
goto short_packet;
uh = udp_hdr(skb);
}
Means if specified length in packet header more large than len in skb, go to
short_packet.
As i know for sure, i have running UDP application which sending packets not
more than 1500 bytes (1480 actually without header), and it is running on
ports 21005, 21004, 21006. There is for sure impossible it will send data
from port 21218 and impossible it will send packet larger than 1480 bytes.
Receiving side is Intel card with hardware checksumming enabled. So in theory
corrupted packets must not bypass hardware checksumming (but probably i am
wrong). Is there anything suspicious and need additional attention?
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
reply other threads:[~2008-01-08 12:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080108123414.M75319@visp.net.lb \
--to=denys@visp.net.lb \
--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).