> Martin, do you *really* need to keep the completely the same codebase for
> kernel and userland?
Well, yes. There are also BeOS and other ports of the driver, and I'd
like to stay them close.
> NTFS uses kmalloc() in way too many places for absolutely no reason,
> as far as kernel source counts.
What should I use instead?
I'm not objecting to have two different kinds of malloc in the ntfs
source, say, malloc and important_malloc (which would be both malloc
in user level code).
> Methink it isn't. Looks like the right thing to do is to keep first 16
> inodes permanently in-core (iget() them upon ->read_super() and keep
> pointers them in ntfs_super_info)
That already happens (load_special_files).
> and use normal ->i_sem for locking.
That would be certainly an alternative to a single semaphore. However,
this has the risk of deadlocks.
Regards,
Martin
