[linux-cifs-client] lseek(x, x, SEEK_END ) and the infinite dentry cache

Maximiliano Curia maxy at rivero.com.ar
Thu Dec 29 22:14:32 GMT 2005


On Thursday 29 December 2005 10:44, Maximiliano Curia wrote:
> I think that this might be related to an incorrect way of handling lockings
> from dosemu/clipper, and I'm about to write a testcase in C to confirm
> what's going on.

I wrote two test programs that reproduce a part of my data-loss problem, both 
test failed, even on a 2.6.15-rc5. I'm not not an expert on record locking 
programming, so I might be making a mistake. Please take a look of them.

The tests wait to have another client to start appending data to a file.
The append is made with a lseek and a write. The main difference between the 
test is that in "tlocks1" I lock the whole file and in "tlocks" just the 
record and a lock in the first byte of the file is used as a sem.

I don't know how to code an equivalent example in win32.

Any suggestion would be appreciated.

-- 
Saludos,
 /\/\ /\ >< `/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tlocks.c
Type: text/x-csrc
Size: 3067 bytes
Desc: not available
Url : http://lists.samba.org/archive/linux-cifs-client/attachments/20051229/c41aa20d/tlocks.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tlocks1.c
Type: text/x-csrc
Size: 3138 bytes
Desc: not available
Url : http://lists.samba.org/archive/linux-cifs-client/attachments/20051229/c41aa20d/tlocks1.bin
-------------- next part --------------
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.8/215 - Release Date: 27/12/05


More information about the linux-cifs-client mailing list