lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090204124011.GA22288@gondor.apana.org.au>
Date:	Wed, 4 Feb 2009 23:40:11 +1100
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	netdev@...r.kernel.org
Subject: Re: GSO checksum warning debug info

On Tue, Feb 03, 2009 at 04:23:45PM -0800, Chris Wright wrote:
> I'm able to trigger the GSO checksum warning, and after 67fd1a73 "net: Add
> debug info to track down GSO checksum bug" here's the more verbose output:
> 
> e1000e: caps=(0x1119a9, 0x0) len=2960 data_len=0 ip_summed=0
> 
> What info would be helpful for you (couple full backtraces below)?

Interesting.  Is this a Linux guest or a Window guest?

If it's a Linux guest, it means that somewhere along the line
the partial checksum got lost.  But I can't see anything obvious.
Since you can reproduce this, could you add some printks along
the path shown in the back trace to see where ip_summed gets
zapped? So that would be tun and bridge basically.

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ