« Return to Thread: Odd write usage

Re: Odd write usage

by Miklos Szeredi :: Rate this Message:

Reply to Author | View in Thread

On Tue, 22 Jul 2008, Daniel Benamy wrote:

> On Saturday 19 July 2008 03:54:14 Miklos Szeredi wrote:
> > On Fri, 18 Jul 2008, Daniel Benamy wrote:
> > > In my filesystem, I don't pass the length of buf in size. Instead I
> > > specify one of a couple of constants as the size which tells the fs
> > > what to do. Buf is a shorter, null terminated string (shorter than
> > > the value passed as size).  This works correctly; valgrind doesn't
> > > show memory errors. Is this behavior supported? Ie, should it
> > > continue to work or might it suddenly break in a future version?
> >
> > Sounds pretty weird.
> >
> > Why not pass the "command" as the first few bytes of the buffer,
> > instead of encoding it in the length?
>
> There's an existing kernel filesystem which has this interface

Curious, which one?

Miklos

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
fuse-devel mailing list
fuse-devel@...
https://lists.sourceforge.net/lists/listinfo/fuse-devel

 « Return to Thread: Odd write usage

LightInTheBox - Buy quality products at wholesale price!