netdev - Re: GSO checksum warning debug info

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: <20090204161155.GG5220@sequoia.sous-sol.org>
Date:	Wed, 4 Feb 2009 08:11:55 -0800
From:	Chris Wright <chrisw@...s-sol.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	Chris Wright <chrisw@...s-sol.org>, netdev@...r.kernel.org
Subject: Re: GSO checksum warning debug info

* Herbert Xu (herbert@...dor.apana.org.au) wrote:
> 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?

Windows 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.

Sure.

thanks,
-chris
--
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