[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130324051325.GE17948@order.stressinduktion.org>
Date: Sun, 24 Mar 2013 06:13:25 +0100
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
To: "Huang, Xiong" <xiong@....qualcomm.com>
Cc: Sven Hartge <sven@...nhartge.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Atheros Communications Inc. AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0) 1.0.0.7 md5/sha1 corrupted using NFS and samba (updated) Version 2
On Sun, Mar 24, 2013 at 04:54:46AM +0000, Huang, Xiong wrote:
>
> >
> > >
> > > if (((pkt_flags & RRS_IS_IPV4) && ((pkt_flags & RRS_IS_TCP) ||
> > (pkt_flags & RRS_IS_UDP))) {
> > > if (pkt_flags & RRS_IS_802_3)
> > > head_len += 8;
> > > iph = (struct iphdr *) (packet + head_len);
> > > if ((iph->frag_off != 0 || (pkt_flags & RRS_IS_IP_FRAG))
> > && !(pkt_flags & RRS_IS_IP_DF))
> > > goto hw_xsum;
> > > }
> > > if (!(err_flags & (RRS_ERR_IP_CSUM | RRS_ERR_L4_CSUM))) {
> > > skb->ip_summed = CHECKSUM_UNNECESSARY;
> > > return;
> > > }
> >
> > Btw the captured corrupted packets are ordinary non-fragmented TCP IPv4
> > packets. But perhaps these flags are dual-use?
> >
> Not dual-use. You could check flags for corrupted packets and compare it with good packet.
> Your corrupted packet is just TCP checksum error ?
I'll try it.
The caputered packets show that a 16 byte segment overwrites later data in the
same packet, sometimes even multiple contiguous 16 byte segments.
The corrupted packets look like this:
...ABC....DBBEF..
Each character represents a 16 byte region, the dots are dont-care
placeholders. The BB-region is overwritten by the data of the first
B-region.
Thanks,
Hannes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists