kernel 2.6.4 and nfs lockd.udpport?

kernel 2.6.4 and nfs lockd.udpport?

[Jan Kesten]

Hi all! 

I'm running a 2.6.4 kernel with compiled in nfs support. I have to tie the 
used ports because there is a firewall to gro through. mountd, statd and 
rquotad are just fine, I can change ports after booting, no problem. But not 
for lockd (or nlockmgr), since AFAIK this must be done with boot parameters. 

I read the docs and found that the parameters sould be lockd.udpport and 
lockd.tcpport=xxx - but this doesn't work. While booting I got errors that 
both are unknown boot options. 

Where is my mistake? 

Cheers,
Jan

Re: kernel 2.6.4 and nfs lockd.udpport?

[Trond Myklebust]

På må , 29/03/2004 klokka 04:58, skreiv Jan Kesten:
> Hi all! 
> 
> I'm running a 2.6.4 kernel with compiled in nfs support. I have to tie the 
> used ports because there is a firewall to gro through. mountd, statd and 
> rquotad are just fine, I can change ports after booting, no problem. But not 
> for lockd (or nlockmgr), since AFAIK this must be done with boot parameters. 
> 
> I read the docs and found that the parameters sould be lockd.udpport and 
> lockd.tcpport=xxx - but this doesn't work. While booting I got errors that 
> both are unknown boot options. 
> 
> Where is my mistake? 

Someone updated lockd so that it uses a sysctl-based interface instead.
Apparently without changing the docs.

See the contents of /proc/sys/fs/nfs ...

Cheers,
  Trond

Re: kernel 2.6.4 and nfs lockd.udpport?

[Jamie Lokier]

Trond Myklebust wrote:
> > I read the docs and found that the parameters sould be lockd.udpport and 
> > lockd.tcpport=xxx - but this doesn't work. While booting I got errors that 
> > both are unknown boot options. 
> > 
> > Where is my mistake? 
> 
> Someone updated lockd so that it uses a sysctl-based interface instead.
> Apparently without changing the docs.

I added the sysctl-based interface, and kept the modules parameters,
and updated the code in line with the 2.6 module parameter style.
See the "module_param_call" lines in fs/lockd/svc.c.

The module parameters "nlm_udpport" and "nlm_tcpport" _do_ work -- I
use them with my firewall.

For some reason, because modules don't need #ifdef MODULE any more, I
thought module_param*() entries would be automatically available as
boot parameters.  Silly me, that would be too obvious.

-- Jamie

Re: kernel 2.6.4 and nfs lockd.udpport?

[Trond Myklebust]

On Wed, 2004-03-31 at 09:57, Jamie Lokier wrote:

> The module parameters "nlm_udpport" and "nlm_tcpport" _do_ work -- I
> use them with my firewall.
> 
> For some reason, because modules don't need #ifdef MODULE any more, I
> thought module_param*() entries would be automatically available as
> boot parameters.  Silly me, that would be too obvious.

module_param*() ought indeed to suffice.

AFAICS the only problem here is that Documentation/kernel-parameters.txt
still lists lockd.udpport and lockd.tcpport instead of the new names
lockd.nlm_udpport and lockd.nlm_udpport.
There is also lockd.nlm_grace_period, and lockd.nlm_timeout, both of
which need to be added to the same list...

Cheers,
  Trond

-- 
Trond Myklebust <trond.myklebust@fys.uio.no>