kern/56461: FreeBSD client rpc.lockd incompatible with Linux server rpc.lockd

Alfred Perlstein alfred at freebsd.org
Fri Jun 18 21:19:58 GMT 2004


* Barney Wolff <barney at databus.com> [040618 14:09] wrote:
> On Fri, Jun 18, 2004 at 10:51:21AM -0700, Alfred Perlstein wrote:
> > 
> > *Sigh* make it a sysctl, but can someone please lay the smack
> > down on the linuxiots and have them fix thier crap?
> > 
> > * Bruce M Simpson <bms at spc.org> [040618 04:50] wrote:
> > > 
> > > Linux NFS advisory locks are broken and incompatible with the rest
> > > of the world. FreeBSD 5.x in particular uses BSD/OS derived NFS code
> > > and thus is affected. FreeBSD 4.x does not implement client-side NFS
> > > advisory locks.
> > > 
> > > This problem is also documented as existing for MacOS X, IRIX and BSD/OS:
> > > http://www.netsys.com/bsdi-users/2002-04/msg00036.html
> > > http://www.uwsg.iu.edu/hypermail/linux/kernel/0311.0/0498.html
> > > http://lists.freebsd.org/pipermail/freebsd-hackers/2003-July/001833.html
> > > http://lists.freebsd.org/pipermail/freebsd-hackers/2003-April/000592.html
> > > 
> > > The patch provided in the PR is verified to solve the problem, but
> > > it would be good to make this functionality optional at run-time,
> > > as many people are likely to be using Linux NFS shares read/write
> > > with advisory locks.
> 
> Pardon an ignorant question, but what happens to unfortunate people who
> have to talk to both Linux and non-quirky servers at the same time?  Is
> there a way to detect what flavor of server you're talking to and adjust
> accordingly?  That would be far better than a sysctl.

Mount option?  Can we do that these days?

-- 
- Alfred Perlstein
- Research Engineering Development Inc.
- email: bright at mu.org cell: 408-480-4684


More information about the freebsd-net mailing list