Well, That maybe a better idea then what we do - we'll try it.
Thnx, Menny -----Original Message----- From: Trond Myklebust [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 7:04 PM To: Menny Hamburger Cc: Neil Brown; [email protected] Subject: RE: [PATCH] NLM program ID for user space NLM server On Thu, 2007-05-10 at 19:45 +0300, Menny Hamburger wrote: > Yes, but in our case we don't care. This is a dedicated server where > we don't see any usage for NLM client. We just want to prevent the > kernel from taking the port in case of some accidental NFS mount that > ommitted 'nolock'. Which is _wrong_. If you omit the 'nolock' mount option, then the client _does_ use NLM locking, and so will need the RPC downcall. If you don't need NLM locking, and want to make sure nobody else can enable it, then you can triviall 'fix' this on your server by patching it to force the nolock mount option. This isn't a patch that we particularly want to see in mainline, though. Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
