All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: nfs@lists.sourceforge.net
Cc: linuxppc64-dev@lists.linuxppc.org
Subject: Re: 2.6.0-test10, oops in nfs_kill_super
Date: Thu, 27 Nov 2003 18:02:04 +0100	[thread overview]
Message-ID: <20031127170204.GA14765@suse.de> (raw)
In-Reply-To: <20031127162511.GA15901@suse.de>

 On Thu, Nov 27, Olaf Hering wrote:

> It dies in invalidate_list()
>                 next = next->next;
> 
> However, why does r3 and r27 differ even if they should be the same?

Scratch that, its a loop...

-- 
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2003-11-27 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 16:25 2.6.0-test10, oops in nfs_kill_super Olaf Hering
2003-11-27 17:02 ` Olaf Hering [this message]

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=20031127170204.GA14765@suse.de \
    --to=olh@suse.de \
    --cc=linuxppc64-dev@lists.linuxppc.org \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.