linux-kernel - Re: [PATCH] NLM program ID for user space NLM server

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <17986.60861.587591.548652@notabene.brown>
Date:	Thu, 10 May 2007 20:02:37 +1000
From:	Neil Brown <neilb@...e.de>
To:	"Menny Hamburger" <menny@...net.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] NLM program ID for user space NLM server

On Thursday May 10, menny@...net.com wrote:
> Hi,
> 
> Since the current kernel cannot be compiled with NFS client and without
> lockd, it is not possible to register a user space NLM server
> Without colliding with the kernel service registered in
> .../fs/lockd/lockd.c.

This doesn't make any sense to me at all.
You can certainly have the NFS client compiled and even running
without lockd running (if you mount with "-o nolock") and in that case
you are free you register your owner user-space NLM server (though I'm
not sure what good it would do you).

And if you want to mount an NFS filesystem without "-o nolock", then
you really need the kernel lockd running, or locking will not work.

Can you explain what you are trying to do - I'm curious.

>  
> +#ifndef 
>  #define NLM_PROGRAM		100021
> +#endif

Uhm...  Do you mean

  +#ifndef NLM_PROGRAM

??  Still not sure how that helps.

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