Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-06 Thread David Thompson
Derrick J Brashear wrote: > > ok, so does the thing trying to set the lock have "k" > permission on the > dir? > > yes, the difference is the "old" kernel never tried. but why > does the new > kernel lose? Issue resolved. "Oh, you mean you have to have the lock acl permission to create a lock?" Y

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread Derrick J Brashear
On Wed, 1 Dec 2004, David Thompson wrote: The command I used on the clients was: tcpdump -vv -s 1500 port 7001 Hope that's right... Doesn't matter. the traffic will all be from port 7001 to port 7000, and back. Box 2 (failure): 14:57:52.434114 tortoise.cs.wisc.edu.af

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread David Thompson
Derrick J Brashear wrote: >On Wed, 1 Dec 2004, David Thompson wrote: > >> time 962.599815, pid 21833: Open 0x422de2c4 flags 0x0 >> time 962.599815, pid 21833: Open 0x422de2c4 flags 0xf423f >> time 962.599815, pid 21833: Analyze RPC op 13 conn 0x2128b4c0 code 0xd user >> 0x417529fa >> time 962.59981

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread Derrick J Brashear
On Wed, 1 Dec 2004, David Thompson wrote: time 962.599815, pid 21833: Open 0x422de2c4 flags 0x0 time 962.599815, pid 21833: Open 0x422de2c4 flags 0xf423f time 962.599815, pid 21833: Analyze RPC op 13 conn 0x2128b4c0 code 0xd user 0x417529fa time 962.599815, pid 21833: Returning code 13 from 1 time

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread David Thompson
Derrick J Brashear wrote: > >fine, so i'll guess this function calls one of our ops (getattr?) and >somehow loses, because EACCES shouldn't be coming from afs_lockctl (at >least not directly) > >Can you fstrace both cases? Here's the sample C program I'm using: #include #include #include #in

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread Derrick J Brashear
Ew, a widereply. Perchance does one support 64 bit locks (F_GETLK64) and the other doesn't? Box 2 (flock doesn't work per the man page): open("/s/db-apps/lib/GradApp/lib/GradApp.pbk", O_RDONLY|O_LARGEFILE) = 4 ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfffae08) = -1 EINVAL (Invalid argumen t) _ll

[CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread David Thompson
Derrick J Brashear wrote: >On Fri, 29 Oct 2004, David Thompson wrote: > >> The ACLs on the directory give this user read acess but no write. >> Like I said, the openafs code is the same on both boxes. >> >> Has anyone seen anything like this? Is this a kernel change? > >Perchance does one support