Ayush RanjanandgVisor bot 9e66f710de Delete devtmpfs and replace it with tmpfs. ...

Our devtmpfs implementation uses the same tmpfs filesystem instance for all
devtmpfs mounts in the sandbox. This would mean that devices mounted in a
container are visible and accessible to all other containers in the sandbox.

With GPU/TPU, the contents of devtmpfs can be different for different
containers within the same sandbox. So it is important to not share the same
devtmpfs contents.

It is better to drop support for devtmpfs, than to implement it incorrectly.
Instead, this change introduces a new dummy filesystem type named `dev`. This
filesystem can not be mounted or listed by the application. This filesystem
creates a new tmpfs instance on GetFilesystem() and populates it with all the
device files.

PiperOrigin-RevId: 578969556

2023-11-02 13:58:58 -07:00

..

BUILD

Delete devtmpfs and replace it with tmpfs.

2023-11-02 13:58:58 -07:00

dev_test.go

Delete devtmpfs and replace it with tmpfs.

2023-11-02 13:58:58 -07:00

dev.go

Delete devtmpfs and replace it with tmpfs.

2023-11-02 13:58:58 -07:00