mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ion Badulescu <ionut@badula.org>
To: Hendrik Visage <hvjunk@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Starfire (Adaptec) kernel 2.6.13+ panics on AMD64 NFS server
Date: Fri, 30 Sep 2005 16:55:19 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0509301635020.13733@ionlinux.tower-research.com> (raw)
In-Reply-To: <d93f04c70509301310y4bde1189wbcaef40124af6766@mail.gmail.com>

On Fri, 30 Sep 2005, Hendrik Visage wrote:

> Anycase, here is a non-PREEMPT traceback.

Same trace, pretty much like I expected. Still, starfire must be getting 
a bad skb from the upper layers, because it gets passed __unmodified__ to 
skb_checksum_help().

Either that, or skb_checksum_help() itself got broken at some point, at 
least on 64-bit platforms.

I'll try to reproduce it over the weekend (assumming I can get an x86_64 
box set up, with a starfire inside) and see where the problem is.

> What makes this one interesting, is that in the preempt case, I had to 
> push the NFS output to get the panic, but the non-preempt case attached, 
> sorta just happened, ie. when the clients just checked on the server's 
> status :(

I'm actually surprised you got your panic from nfsd. skb_checksum_help() 
is called only when one of the fragments has length == 1, so the easiest 
way to hit it is to slowly type something into a telnet session.

Thanks,
Ion

-- 
   It is better to keep your mouth shut and be thought a fool,
             than to open it and remove all doubt.

  reply	other threads:[~2005-09-30 20:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30  3:36 Hendrik Visage
2005-09-30  4:16 ` Andrew Morton
2005-09-30  8:14   ` Hendrik Visage
2005-09-30 16:46     ` Ion Badulescu
2005-09-30 16:01   ` Hendrik Visage
2005-09-30 17:40     ` Andrew Morton
2005-09-30 20:10       ` Hendrik Visage
2005-09-30 20:55         ` Ion Badulescu [this message]
2005-09-30 22:39         ` Herbert Xu
2005-10-01 19:21           ` Hendrik Visage

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=Pine.LNX.4.61.0509301635020.13733@ionlinux.tower-research.com \
    --to=ionut@badula.org \
    --cc=akpm@osdl.org \
    --cc=hvjunk@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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

all inboxes | Powered by JetHome®