Re: [PATCH v5 3/4] ipv4: Namespaceify tcp_fastopen_key knob

2017-09-28 Thread David Miller
From: Haishuang Yan Date: Wed, 27 Sep 2017 11:35:42 +0800 > Different namespace application might require different tcp_fastopen_key > independently of the host. > > David Miller pointed out there is a leak without releasing the context > of tcp_fastopen_key during netns teardown. So add the rel

[PATCH v5 3/4] ipv4: Namespaceify tcp_fastopen_key knob

2017-09-26 Thread Haishuang Yan
Different namespace application might require different tcp_fastopen_key independently of the host. David Miller pointed out there is a leak without releasing the context of tcp_fastopen_key during netns teardown. So add the release action in exit_batch path. Tested: 1. Container namespace: # cat