From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org, Shirish Kalele <kalele@veritas.com>,
NFS maillist <nfs@lists.sourceforge.net>
Subject: Re: knfsd over TCP (was RE: 2.4.18pre2aa1)
Date: 08 Jan 2002 16:40:33 +0100 [thread overview]
Message-ID: <shs7kqsu9zi.fsf@charged.uio.no> (raw)
In-Reply-To: <20020108155553.A1894@inspiron.school.suse.de>
In-Reply-To: <20020108155553.A1894@inspiron.school.suse.de>
>>>>> " " == Andrea Arcangeli <andrea@suse.de> writes:
> NFS updates from Trond Myklebust. BTW, the svc tcp patches are
> broken, they oopsed on me with a simple mount of nfs via udp,
> so I left them out. this is the oops for the record:
Duh...
sunrpc still hasn't been updated to use module_init(), so
initialization of the new buffer slab was only working when you used
the thing as a module. Sorry for not having spotted that one.
I've put out a fixed copy of the knfsd over TCP patch (and the NFS_ALL
patch).
Cheers,
Trond
next prev parent reply other threads:[~2002-01-08 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 14:55 2.4.18pre2aa1 Andrea Arcangeli
2002-01-08 15:40 ` Trond Myklebust [this message]
2002-01-08 15:47 ` knfsd over TCP (was RE: 2.4.18pre2aa1) Andrea Arcangeli
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=shs7kqsu9zi.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=andrea@suse.de \
--cc=kalele@veritas.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox