Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 05 May 2020 11:48:25 -0700 (PDT)
Message-Id: <20200505.114825.1476000329624313198.davem@davemloft.net>
To:     sjpark@amazon.com
Cc:     viro@zeniv.linux.org.uk, kuba@kernel.org,
        gregkh@linuxfoundation.org, edumazet@google.com,
        sj38.park@gmail.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, sjpark@amazon.de
Subject: Re: [PATCH net v2 0/2] Revert the 'socket_alloc' life cycle change
From:   David Miller <davem@davemloft.net>
In-Reply-To: <20200505081035.7436-1-sjpark@amazon.com>
References: <20200505081035.7436-1-sjpark@amazon.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: SeongJae Park <sjpark@amazon.com>
Date: Tue, 5 May 2020 10:10:33 +0200

> From: SeongJae Park <sjpark@amazon.de>
> 
> The commit 6d7855c54e1e ("sockfs: switch to ->free_inode()") made the
> deallocation of 'socket_alloc' to be done asynchronously using RCU, as
> same to 'sock.wq'.  And the following commit 333f7909a857 ("coallocate
> socket_sq with socket itself") made those to have same life cycle.
> 
> The changes made the code much more simple, but also made 'socket_alloc'
> live longer than before.  For the reason, user programs intensively
> repeating allocations and deallocations of sockets could cause memory
> pressure on recent kernels.
> 
> To avoid the problem, this commit reverts the changes.

Series applied and queued up for -stable, thanks.