Hi Eric, Thanks for your reply. Can you please let me know the patch for this fix or kernel version where the fix was integrated. Regards 25krishna -----Original Message----- From: containers-bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx [mailto:containers-bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Eric W. Biederman Sent: Thursday, July 28, 2016 6:52 PM To: Madhukrishna G <madhukrishna.g@xxxxxxx> Cc: containers@xxxxxxxxxxxxxxxxxxxxxxxxxx Subject: Re: sysctl variables are not available to newly created namespace "G, Madhukrishna" <madhukrishna.g@xxxxxxx> writes: > Hi, > > In my current linux 3.2.71 stable version , I have created a network > namespace and when I listed sysctl variables in following directory > " /proc/sys/net/core/" am able to see net.core.xfrm* variables only, > i.e only CONFIG_SYSCTL related variables, even though I have enabled > CONFIG_NET as well as CONFIG_NET_NS I am not able to see any sysctl > variables related to ne.core(rmem_max, wmem_max, rmem_default and > wmem_default). > The only networking sysctls that are shown are the networking sysctls that are local to your network namespace (unless you are in the initial network namespace). > #<mailto:root@ned4g8:/home/gmadhuk/linux-3.16-clim-3.16.7-clim#> ip > netns exec gmk1 ls -l /proc/sys/net/core/ total 0 > -rw-r--r-- 1 root root 0 Jul 25 03:01 somaxconn > -rw-r--r-- 1 root root 0 Jul 25 03:01 xfrm_acq_expires > -rw-r--r-- 1 root root 0 Jul 25 03:01 xfrm_aevent_etime > -rw-r--r-- 1 root root 0 Jul 25 03:01 xfrm_aevent_rseqth > -rw-r--r-- 1 root root 0 Jul 25 03:01 xfrm_larval_drop > > > Where as in my older kernel version, it will show all sysctl variables. > # ls -l /proc/sys/net/core/ > total 0 > -rw-r--r-- 1 root root 0 Jul 20 05:40 busy_poll > -rw-r--r-- 1 root root 0 Jul 20 05:40 busy_read > -rw-r--r-- 1 root root 0 Jul 20 05:40 default_qdisc > -rw-r--r-- 1 root root 0 Jul 20 05:40 dev_weight > -rw-r--r-- 1 root root 0 Jul 20 05:40 flow_limit_cpu_bitmap > -rw-r--r-- 1 root root 0 Jul 20 05:40 flow_limit_table_len > -rw-r--r-- 1 root root 0 Jul 20 05:40 message_burst > -rw-r--r-- 1 root root 0 Jul 20 05:40 message_cost > -rw-r--r-- 1 root root 0 Jul 20 05:40 netdev_budget > -rw-r--r-- 1 root root 0 Jul 20 05:40 netdev_max_backlog > -rw-r--r-- 1 root root 0 Jul 20 05:40 netdev_tstamp_prequeue > -rw-r--r-- 1 root root 0 Jul 20 05:40 optmem_max > -rw-r--r-- 1 root root 0 Jul 20 05:40 rmem_default > -rw-r--r-- 1 root root 0 Jul 20 05:40 rmem_max > -rw-r--r-- 1 root root 0 Jul 20 05:40 rps_sock_flow_entries > -rw-r--r-- 1 root root 0 Jul 20 05:40 somaxconn > -rw-r--r-- 1 root root 0 Jul 20 05:40 warnings > -rw-r--r-- 1 root root 0 Jul 20 05:40 wmem_default > -rw-r--r-- 1 root root 0 Jul 20 05:40 wmem_max > -rw-r--r-- 1 root root 0 Jul 20 05:40 xfrm_acq_expires > -rw-r--r-- 1 root root 0 Jul 20 05:40 xfrm_aevent_etime > -rw-r--r-- 1 root root 0 Jul 20 05:40 xfrm_aevent_rseqth > -rw-r--r-- 1 root root 0 Jul 20 05:40 xfrm_larval_drop Yep. That was a bug, now fixed. Eric _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers Information transmitted by this e-mail is proprietary to Mphasis, its associated companies and/ or its customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at mailmaster@xxxxxxxxxxx and delete this mail from your records. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
