Explain the cmdline argument exceed_file_max_panic in the file Documentation/admin-guide/sysctl/fs.rst
Signed-off-by: Tiezhu Yang <yangtie...@loongson.cn> --- Documentation/admin-guide/sysctl/fs.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/admin-guide/sysctl/fs.rst b/Documentation/admin-guide/sysctl/fs.rst index 2a45119..0cfc5c4 100644 --- a/Documentation/admin-guide/sysctl/fs.rst +++ b/Documentation/admin-guide/sysctl/fs.rst @@ -126,6 +126,13 @@ Attempts to allocate more file descriptors than file-max are reported with printk, look for "VFS: file-max limit <number> reached". +If there exists file descriptor leaks, when file-max limit reached, +we can see that the system can not work well and at worst the user +can do nothing, it is even impossible to execute reboot command due +to too many open files in system. In order to reboot automatically +to recover to the normal status, we can use the cmdline argument +exceed_file_max_panic to control whether to call panic in this case. + nr_open ------- -- 2.1.0
