From: Valient G. <vg...@po...> - 2004-06-22 11:53:22
|
Are you running in single-threaded mode, or in threaded mode? By default FUSE is running in threaded mode - is it possible you have a race condition accessing your cache? Valient On Tue, 2004-06-22 at 11:38, Franco Broi wrote: > Hi chaps > > Can anyone help explain what might be happening with my fuse filesystem? > > I've built an implementation based on the example fusexmp.c but with > file descriptor caching to avoid having to keep opening and closing > files for reads and writes. > > I'm using the latest source from CVS. > > It seemed like it was working but then strange things started to happen. > > After running an application which simultaneously opens many files, some > data being returned was being corrupted. The corruption is always the > same, a block of data from the wrong file is being returned immediately > after the file is opened, then all the rest of the file is returned > correctly. I traced the program and discovered that after the open the > read routine was not being called, therefore the data must be cached. > > I waiting some time for the cache to expire and did the same test, this > time the data was returned correctly. > > Any ideas anybody? > > Thanks > Franco > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Avf-fuse-dev mailing list > Avf...@li... > https://lists.sourceforge.net/lists/listinfo/avf-fuse-dev > |