Chirantan Ekbote aa77ea4045 linux.rs: Don't use /proc/sys/fs/file-max ... Don't use /proc/sys/fs/file-max when setting the max open file limit for the virtio-fs device. This will fail when the value is larger than the hard limit set for the crosvm process, unless it also has CAP_SYS_ADMIN in the initial namespace. Instead, just use the hard limit as returned by `prlimit64`. Increasing the soft limit up to the hard limit is allowed even for completely unprivileged processes. It is up to the process that spawned crosvm to ensure that the hard limit is high enough that the virtio-fs server will not run out of fds. BUG=b:142344095 TEST=Start a termina VM with a virtio-fs device after applying CL:1939193 Change-Id: I4fb4c33ffe6378ed3109fddcb0fc2bf3da850252 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1957767 Tested-by: Chirantan Ekbote <chirantan@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Auto-Submit: Chirantan Ekbote <chirantan@chromium.org> Commit-Queue: Stephen Barber <smbarber@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org>		2019-12-09 23:39:16 +00:00
..
plugin
argument.rs	Adds a flag_or_value command line argument option	2019-12-09 22:36:59 +00:00
crosvm.rs	linux: check memory size calculation overflow	2019-12-06 09:37:52 +00:00
linux.rs	linux.rs: Don't use /proc/sys/fs/file-max	2019-12-09 23:39:16 +00:00
main.rs
panic_hook.rs