First of all, since 2.5.5-pre1 there is an up-to-date guide for
porting filesystems from 2.4 to 2.5.<latest>. Location:
It WILL be kept up-to-date. IOW, submit an API change that may require
filesystem changes without a corresponding patch to that file and I will
hunt you down and hurt you. Badly.
The same document covers "what do I need to change to keep my out-of-tree
filesystem uptodate". So watch for changes there.
Normally when API change happens, the person doing it is responsible for
updating all in-tree filesystems or, at least, warning people about the
breakage. Applying the list of broken filesystems.
Right now that list consists of umsdos and intermezzo. The former will
be fixed after the next series of file_system_type cleanups. The latter
is a victim of current changes in locking scheme. Help from intermezzo
folks would be a good idea - preferably in the form that would reduce
the dependency on the VFS guts.
New locking scheme is described in Documentation/filesystems/directory-locking.
In details and with proof of correctness.
It doesn't change the exclusion warranties for filesystems, so unless they
mess with locking in non-trivial ways (intermezzo was the only in-tree
example) they shouldn't need any changes. Some things might become simpler,
actually (i.e. in some cases private locking became redundant and can be
dropped). Again, see Documentation/filesystems/porting for details of
Documentation/filesystems/Locking is slowly getting up-to-date. Descriptions
of several superblock methods are still missing and I would really appreciate
it if folks who had introduced them would document them.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:01:05 EST