public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders Peter Fugmann <afu@fugmann.dhs.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre4-ac1
Date: Wed, 27 Mar 2002 00:45:33 +0100	[thread overview]
Message-ID: <3CA1081D.7040101@fugmann.dhs.org> (raw)
In-Reply-To: <E16pvYV-0003cD-00@the-village.bc.nu>	<3CA0EAAA.8000400@fugmann.dhs.org> <15520.61687.962869.841296@notabene.cse.unsw.edu.au>

Thanks.

It seems that there is some more problems.
I have not verified the lookup (since I just booted right away with the patch), but
I have found that:

Mar 26 23:56:58 gw kernel: nfsd: LOOKUP(3)   24: 03000001 03000900 00000002 0000106d 0000106c 0000070d WMRootMenu
Mar 26 23:56:58 gw kernel: RPC request reserved 240 but used 244

Mar 27 00:30:09 gw kernel: nfsd: CREATE(3)   24: 03000001 03000900 00000002 00000003 00000002 00000000 test
Mar 27 00:30:09 gw kernel: RPC request reserved 272 but used 276

Mar 27 00:30:21 gw kernel: nfsd: SYMLINK(3)  24: 03000001 03000900 00000002 00000003 00000002 00000000 test1 -> test
Mar 27 00:30:21 gw kernel: RPC request reserved 272 but used 276

And there might be others.

I would be happy to post a patch, but I do not know the
exact reason for the calculations in struct svc_procedure.
I guess that it has to do with how the request is constructed.

Regards
Anders Fugmann





  reply	other threads:[~2002-03-26 23:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26 18:20 Linux 2.4.19pre4-ac1 Alan Cox
2002-03-26 21:39 ` Anders Peter Fugmann
2002-03-26 22:06   ` Neil Brown
2002-03-26 23:45     ` Anders Peter Fugmann [this message]
2002-03-27  2:07       ` Neil Brown
2002-03-27  2:29         ` Mike Fedyk
2002-03-27 12:18         ` Anders Peter Fugmann
2002-03-27  2:47 ` Mike Fedyk
  -- strict thread matches above, loose matches on Subject: below --
2002-03-26 18:34 Dana Lacoste
2002-03-26 18:56 ` Alan Cox
2002-03-27  3:23 Neil Brown
2002-03-27 14:29 ` Bill Davidsen

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=3CA1081D.7040101@fugmann.dhs.org \
    --to=afu@fugmann.dhs.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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