Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]

To: debian-kernel@lists.debian.org
Cc: 377024@bugs.debian.org, control@bugs.debian.org
Subject: Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]
From: jeanmichel.123@free.fr
Date: Fri, 07 Jul 2006 20:53:49 +0200
Message-id: <[🔎] 1152298429.44aeadbd93204@imp2-g19.free.fr>
Reply-to: jeanmichel.123@free.fr, 377024@bugs.debian.org
In-reply-to: <20060706173030.GA28133@uio.no>
References: <20060706092623.21458.325.reportbug@localhost.internal.isoscope.com> <20060706173030.GA28133@uio.no>

I just find a relation between the bad checksum and lenth:

I have seen:
bad checksum: 5a1c , when Len is 120
bad checksum: 5f58 , when Len is 1460
bad checksum: 5e1c , when Len is 1144
bad checksum: 5a28 , when Len is 132

This seams to mean that:

checksum= 0x59A4 + Len

but why on earth do I have this bug?

Reply to:

Follow-Ups:
- Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]
  - From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>

Prev by Date: Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]
Next by Date: Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]
Previous by thread: Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]
Next by thread: Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]
Index(es):
- Date
- Thread