Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-15 Thread Steve Dickson
Chuck Lever wrote: On Oct 9, 2008, at Oct 9, 2008, 11:48 AM, Steve Dickson wrote: Unfortunately, I'm failing miserably on reproducing this... Here is what I've done: Chuck Lever wrote: Hi Steve- As I understand it, the documented bug refers to running nfs-utils 1.1.3 on kernels older

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-15 Thread Steve Dickson
Chuck Lever wrote: Easy... the mount.nfs subcommand in nfs-utils-1.1.3 switches to legacy mode on old kernels (pre 2.6.23). What I meant by you need to force the use of the legacy mount command is that you need to force the use of the legacy binary mount interface. I have tried a legacy FC-5

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-15 Thread Steve Dickson
Chuck Lever wrote: Ok... The client has the nfs-utils-1.1.3 mount.nfs binary using an FC-7 (2.6.21) kernel. New text mount interface with old binary kernel interface. I have two servers: ServerA has the nfs-utils-1.1.3 rpc.mountd binary using an F-9 2.6.26 kernel ServerB has the

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-15 Thread Chuck Lever
On Oct 15, 2008, at 2:18 PM, Steve Dickson wrote: Chuck Lever wrote: Ok... The client has the nfs-utils-1.1.3 mount.nfs binary using an FC-7 (2.6.21) kernel. New text mount interface with old binary kernel interface. I have two servers: ServerA has the nfs-utils-1.1.3 rpc.mountd binary

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-15 Thread Steve Dickson
Chuck Lever wrote: So where have I gone wrong in reproducing this? What happens when you don't specify a sec= option at all? 'touch /mnt/home/tmp/foo rm /mnt/home/tmp/foo' works as expected... I'm out of ideas then. Me too... :( The problem was with the mount command in nfs-utils

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-15 Thread Chuck Lever
On Oct 15, 2008, at 12:57 PM, Steve Dickson wrote: Chuck Lever wrote: Easy... the mount.nfs subcommand in nfs-utils-1.1.3 switches to legacy mode on old kernels (pre 2.6.23). What I meant by you need to force the use of the legacy mount command is that you need to force the use of the

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-12 Thread Aníbal Monsalve Salazar
On Thu, Oct 09, 2008 at 11:48:08AM -0400, Steve Dickson wrote: Unfortunately, I'm failing miserably on reproducing this... Here is what I've done: Chuck Lever wrote: Hi Steve- As I understand it, the documented bug refers to running nfs-utils 1.1.3 on kernels older than 2.6.22. I created a

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-09 Thread Steve Dickson
Unfortunately, I'm failing miserably on reproducing this... Here is what I've done: Chuck Lever wrote: Hi Steve- As I understand it, the documented bug refers to running nfs-utils 1.1.3 on kernels older than 2.6.22. I created a Fedora 7 KVM guest that runs a 2.6.21 kernel. I installed the

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-06 Thread Rasmus Bøg Hansen
Chuck Lever skrev: Hi Steve- As I understand it, the documented bug refers to running nfs-utils 1.1.3 on kernels older than 2.6.22 (ie the problem is with the legacy mount command, not with the in-kernel mount parser, which has a different, less harmful bug that masks these symptoms). To

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-06 Thread Chuck Lever
On Oct 6, 2008, at 5:12 AM, Rasmus Bøg Hansen wrote: Chuck Lever skrev: Hi Steve- As I understand it, the documented bug refers to running nfs-utils 1.1.3 on kernels older than 2.6.22 (ie the problem is with the legacy mount command, not with the in-kernel mount parser, which has a different,

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-04 Thread Aníbal Monsalve Salazar
On Thu, Oct 02, 2008 at 09:19:58AM -0400, Steve Dickson wrote: Aníbal Monsalve Salazar wrote: In my case I run Debian stable (nfs-utils 1.0.10) on the server and Debian unstable (1.1.3) on the client. I have not tried upgrading the server (which is probably not an option until Debian Lenny is

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-02 Thread Aníbal Monsalve Salazar
On Fri, Aug 08, 2008 at 09:06:46PM -0400, Chuck Lever wrote: Confirmed. The kernel's mountd client doesn't even bother to unmarshal the auth flavor list in the server's reply. I'll work on a fix. Chuck Lever was able to confirm this bug. On Thu, Oct 02, 2008 at 01:30:54PM +0200, Rasmus Bøg

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-02 Thread Steve Dickson
Aníbal Monsalve Salazar wrote: In my case I run Debian stable (nfs-utils 1.0.10) on the server and Debian unstable (1.1.3) on the client. I have not tried upgrading the server (which is probably not an option until Debian Lenny is released), but running the client with sec=sys solves the

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-02 Thread Steve Dickson
What is logged in /var/log/messages you turn on the in-kernel mount debugging via: rpcdebug -m nfs -s mount then do the following three mounts: mount -o sec=none madhat:/home /mnt/home mount -o sec=sys madhat:/home /mnt/home mount madhat:/home /mnt/home I got: Oct 2 09:23:10 rawhat

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-02 Thread Chuck Lever
Hi Steve- As I understand it, the documented bug refers to running nfs-utils 1.1.3 on kernels older than 2.6.22 (ie the problem is with the legacy mount command, not with the in-kernel mount parser, which has a different, less harmful bug that masks these symptoms). To reproduce this you

Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs

2008-10-01 Thread Aníbal Monsalve Salazar
On Tue, Sep 30, 2008 at 11:42:28AM -0400, Steve Dickson wrote: Hey... In the following problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492970 What were the kernel versions on both the client and server? I would like to knock this out before cutting another release of nfs-utils...