rtems filesystem question

[correo at fernando-ruiz.com (Fernando RUIZ CASAS)]

You have reason.

This is a concern that I have not thunk.

Userenv struct has not a 'next' field.

Perhaps a modification to do in getprivateenv().

globaluserenv needs a 'next' field to resolve this silly problem.

BRGDS.

Fernando RUIZ CASAS
home: correo at fernando-ruiz.com

> -----Mensaje original-----
> De: Till Straumann [mailto:strauman at SLAC.Stanford.EDU]
> Enviado el: martes, 15 de octubre de 2002 5:52
> Para: rtems-users at oarcorp.com
> Asunto: rtems filesystem question
> 
> 
> At a first glance, it seems that 'umount()' is not really
> safe. It seems that umount() does not inspect all the
> userenv current_filesystem nodes to verify that no
> thread has its cwd on the FS to be unmounted.
> 
> Also, there seems to be no protection against
> one thread mounting stuff onto (or chdir()ing into)
> a FS which another thread is just about to unmount.
> 
> Am I missing something?
> 
> -- Till
> 
>