Messages in this thread | | | Subject | Re: NFSv3: Summary of recent bugfixes/updates to the NFSv3 patches... | From | Trond Myklebust <> | Date | 01 Sep 1999 10:06:41 +0200 |
| |
"Steven N. Hirsch" <shirsch@adelphia.net> writes:
> On Tue, 31 Aug 1999, Steven N. Hirsch wrote: > > > On 31 Aug 1999, Trond Myklebust wrote: > > > > > The current version of the NFSv3 patches is 0.11.6. It should patch > > > cleanly against stock linux-2.2.10, 2.2.11 and 2.2.12. > > > > Will this apply cleanly to an otherwise-stock 2.2.12 kernel with HJ Lu's > > server patches previously added? > > Following up on my own post. After fixing three small conflicts, they do > apply over HJ's. However, lockd still ooopses immediately when exercising > locks against another server. This is the problem I reported weeks ago.
Are HJ's lockd patches really required on linux-2.2.12? As far as I can see, 'nfsd-2.2.7-1.lock.patch' is already in the kernel.
'nfsd-2.2.7-2.lockd.patch' should in most cases not be necessary, but if you do prefer to start lockd by hand rather than letting NFS do it, then as far as I can see, the only thing that fails is the patch to 'svc.c'. You need to add
do_lockdctl = NULL;
to 'cleanup_module(void)'.
As for the rest of HJ's 2.2.7 patches, I can't see any conflicts with NFSv3. Where are you seeing them?
Cheers, Trond
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |