filesystem WRITE support

From: silverdr (silverdr_at_inet.remove.it.pl)
Date: 08/27/04 

Date: Fri, 27 Aug 2004 21:00:05 +0200

Hi group,

I have written a module that supports a rather simple, yet a bit exotic
custom filesystem under 2.4.x. It currently mounts, umounts, does
statfs, reads files and directories... it is about the time to start
coding the WRITE support for it. Since this is my first fsdevel I would
like to ask what should I be careful about when creating the write
support? I mean e.g. some kind of access locking/semaphores/whatever.
Just what and where (which methods) should contain such things to cope
with e.g. possible race conditions. What else should be taken care of?
Yes, I know I could spend a few weeks reading all the fs' sources trying
to figure it out myself but if someone more experienced could give a
couple of pieces of advice, I would be grateful for saving me some of my
very little free-weekends-time I dedicate to this project... 

-- 
The nice thing about standards is that there are so many of them to 
choose from.

Relevant Pages

  • Re: [PATCH] utimensat implementation
    ... it's in Posix and we have to support it at the library level, ... I'd like to avoid having a big swithc statement in every filesystem, ... This is starting to sound an awful lot like statfs(). ...
    (Linux-Kernel)
  • Re: [RFC] FUSE permission modell (Was: fuse review bits)
    ... > Allowing user mounts with no* should be allways ok (no config needed ... what about separate limits for # of private namespaces ... say I want to support mounting any remote file ... okay" as long as nosuid and nogid are implicit? ...
    (Linux-Kernel)