Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+v4\s+2\/2\]\s+ipvs\:\s+allow\s+some\s+sysctls\s+in\s+non\-init\s+user\s+namespaces\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+v4\s+2\/2\]\s+ipvs\:\s+allow\s+some\s+sysctls\s+in\s+non\-init\s+user\s+namespaces\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [PATCH v4 2/2] ipvs: allow some sysctls in non-init user namespaces (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Mon, 6 May 2024 18:10:48 +0300 (EEST); Hello, Looks good to me for net-next, thanks! Acked-by: Julian Anastasov <ja@xxxxxx> Regards -- Julian Anastasov <ja@xxxxxx>; /html/lvs-devel/2024-05/msg00024.html (15,484 bytes)
2. [PATCH v4 2/2] ipvs: allow some sysctls in non-init user namespaces (score: 1): Author: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@xxxxxxxxxxxxx>; Date: Mon, 6 May 2024 16:14:44 +0200; Let's make all IPVS sysctls writtable even when network namespace is owned by non-initial user namespace. Let's make a few sysctls to be read-only for non-privileged users: - sync_qlen_max - sync_soc; /html/lvs-devel/2024-05/msg00021.html (13,841 bytes)

Current List: 1 - 2
Page: [1]