linux-kernel - Re: nfs file locking broken

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>] [day] [month] [year] [list]

Message-Id: <1161110455.5559.16.camel@lade.trondhjem.org>
Date:	Tue, 17 Oct 2006 14:40:55 -0400
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	"Robert W. Fuller" <garbageout@...global.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: nfs file locking broken

On Tue, 2006-10-17 at 14:30 -0400, Robert W. Fuller wrote:
> Robert W. Fuller wrote:
> > I tried to upgrade from 2.6.16.27 to 2.6.17.13.  I have also tried
> > 2.6.18.1.  I discovered NFS file locking no longer works between a Linux
> > client and an OpenBSD server.  For example, gtk-gnutella gets the
> > following error:
> > 
> > 06-10-14 15:50:19 (WARNING): fcntl(8, F_SETLK, ...) failed for
> > "/home/edison/.gtk-gnutella/gtk-gnutella.pid": Permission denied
> > 
> > gpg hangs waiting for a lock for ~/.gnupg/random_seed
> 
> Maybe the thing to do is to Cc: the NFS guy on this?  Anybody else have
> any suggestions?
> 
> Is there a known fundamental change in the Linux NFS client that would
> break file locking between a Linux NFS client and an OpenBSD-3.8 NFS
> server?    Is OpenBSD-3.8 somehow broken with respect to new behavior in
> the Linux NFS client?
> 
> This is very reproducible.  File locking works with 2.6.16.27.  Sometime
> thereafter it ceased to work.  There are no configuration changes to
> /etc or anything like that....  For me, it's a simple matter of choosing
> a working kernel from the GRUB menu or a broken kernel.

File locking works fine for me, both against Linux boxes and others. I
don't have any OpenBSD servers to test, though.

Have you tried using something like ethereal/wireshark in order to sniff
the wire?

Cheers,
  Trond

-
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/