mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Mike Elmore <mike@kre8tive.org>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again
Date: Fri, 29 Dec 2000 16:47:05 +1300	[thread overview]
Message-ID: <20001229164705.A17269@metastasis.f00f.org> (raw)
In-Reply-To: <20001228161126.A982@lingas.basement.bogus> <200012282159.NAA00929@pizda.ninka.net> <20001228212116.A968@lingas.basement.bogus>
In-Reply-To: <20001228212116.A968@lingas.basement.bogus>; from mike@kre8tive.org on Thu, Dec 28, 2000 at 09:21:16PM -0600

On Thu, Dec 28, 2000 at 09:21:16PM -0600, Mike Elmore wrote:

    Any idea what portion of pre4 got fixed in pre5 to
    fix this problem?  I'd just like to know so I can
    look around if it comes back.

nfs over UDP? My guess is the IP fragmentation fix Alexey posted a
couple of days ago.


  --cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-29  4:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-28 22:11 Mike Elmore
2000-12-28 21:59 ` David S. Miller
2000-12-29  3:21   ` Mike Elmore
2000-12-29  3:47     ` Chris Wedgwood [this message]
2000-12-29  6:15     ` Linus Torvalds
2000-12-29 10:25       ` Chris Wedgwood
2000-12-30 10:42       ` Andrew Morton
2000-12-30 18:06         ` Francois Romieu
2000-12-30 23:01         ` NIC recommendations (was Re: Repeatable 2.4.0-test13-pre4...) Barry K. Nathan
2001-01-01 23:51           ` H. Peter Anvin
2000-12-29  8:14     ` Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again David Ford
2000-12-29  8:51 Ray Strode
2000-12-29 16:15 Jeff Chua

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=20001229164705.A17269@metastasis.f00f.org \
    --to=cw@f00f.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@kre8tive.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®