[...]
> ... and? Suppose that users foo and bar are accessing the file. foo has
> credentials alive and well, but bar got them revoked. Now, foo accesses a
> piece of file. Data is read and cached. Into the inode's i_data. Where bar
> can pick them without any calls to server. See the problem? We are
> _already_ sharing the cache. And since file permissions are _not_
> range-based...
This is what happens with normal filesystems too: If I open the file, and
you then remove my rights on it, I still can putz around. I won't be able
to open it again, that's all.
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/