From 7396fed802c126cbfd3e9c87821fc002cc550cd3 Mon Sep 17 00:00:00 2001 From: Chiachang Wang Date: Thu, 15 Oct 2020 21:09:25 +0800 Subject: [PATCH] Prevent using abstract terms in the property name In many cases, it's a common practice to use the name of the domain type of a process or the type of the usage category instead of using ambiguous terms like sys, system, etc. Update the property name with net. prefix for better naming to fit the usage of the system property. Bug: 170917042 Test: 1. m -j10 2. Check if /proc/sys/net/ipv4/tcp_default_init_rwnd is updated as expected Change-Id: I0267880d62cc504a419827732780d2db97b2dfef --- rootdir/init.rc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rootdir/init.rc b/rootdir/init.rc index 3146f369e..d5b1d7252 100644 --- a/rootdir/init.rc +++ b/rootdir/init.rc @@ -1011,8 +1011,8 @@ on property:sys.sysctl.extra_free_kbytes=* write /proc/sys/vm/extra_free_kbytes ${sys.sysctl.extra_free_kbytes} # "tcp_default_init_rwnd" Is too long! -on property:sys.sysctl.tcp_def_init_rwnd=* - write /proc/sys/net/ipv4/tcp_default_init_rwnd ${sys.sysctl.tcp_def_init_rwnd} +on property:net.tcp_def_init_rwnd=* + write /proc/sys/net/ipv4/tcp_default_init_rwnd ${net.tcp_def_init_rwnd} # perf_event_open syscall security: # Newer kernels have the ability to control the use of the syscall via SELinux