Hi!
> It looks much cleaner than my previous approaches. There seems to be
> something strange with usage counts:
>
> pavel@bug:/tmp/cz1_mbrola.tgz#utar$ ls -al
> total 88
> drwxr-xr-x 2 pavel users 3586 Mar 26 18:43 ./
> drwxrwxrwt 38 root root 81920 Jul 24 09:57 ../
> drwxr-xr-x 42949 pavel users 0 Mar 25 11:16 czech/
> pavel@bug:/tmp/cz1_mbrola.tgz#utar$
It should be the same as '/overlay/tmp/cz1_mbrola.tgz#utar'. If it
is, then its a coda problem.
> Yes. You seem to have damaged locking:
> [...]
>
> In case of !dentry, up(&dir->i_sem) is not executed at all.
Oops. Corrected.
> I have some cleanups to nredir.c module, they are attached (please
> apply). Ouch, and there's slight problem with caching:
>
Thanks for the patch. I've applied it (except the @/# change :).
> You access vmlinux#gz, then load nredir module, then access vmlinux#gz
> again. But failure is already cached and you are out of luck :-(.
Yes you are right. I was thinking of a solution where the kernel
module initialization would kill the negative dentries which contain
the magic char.
Miklos
