All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dylan Griffiths <dylang@thock.com>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4 NFS bug (annoying sylmlinx breakage)
Date: Mon, 14 Jan 2002 15:56:06 -0600	[thread overview]
Message-ID: <3C4353F6.1090709@thock.com> (raw)
In-Reply-To: <3C43447D.9000504@thock.com> <20020114141209.W26688@lynx.adilger.int>

Andreas Dilger wrote:
> Upgrade your kernel before reporting such bugs.  I'm pretty sure it has
> already been fixed.  Something about the NFSv3 calling an inappropriate
> (but similarly named) function in the symlink path.

I've looked at the 2.4.14 nfs fs code as it seemed client side.


         /* We place the length at the beginning of the page,
          * in host byte order, followed by the string.  The
          * XDR response verification will NULL terminate it.
          */


I'm guessing nfs3xdr.c does not have this behaviour the code relies on.  I 
will grab 2.4.17 and see of the code/behaviour is different.

-- 
     www.kuro5hin.org -- technology and culture, from the trenches.
                          -=-=-=-=-=-
Those that give up liberty to obtain safety deserve neither.
  -- Benjamin Franklin
   http://www.zdnet.com/zdnn/stories/news/0,4586,2812463,00.html
   http://slashdot.org/article.pl?sid=01/09/16/1647231
                          -=-=-=-=-=-


      reply	other threads:[~2002-01-14 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 20:50 Linux 2.4 NFS bug (annoying sylmlinx breakage) Dylan Griffiths
2002-01-14 21:12 ` Andreas Dilger
2002-01-14 21:56   ` Dylan Griffiths [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=3C4353F6.1090709@thock.com \
    --to=dylang@thock.com \
    --cc=adilger@turbolabs.com \
    --cc=dylang+kernel@thock.com \
    --cc=linux-kernel@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 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.