From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:34218 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751524AbeCPQbo (ORCPT
        <rfc822;netdev@vger.kernel.org>); Fri, 16 Mar 2018 12:31:44 -0400
Date: Fri, 16 Mar 2018 12:31:42 -0400 (EDT)
Message-Id: <20180316.123142.2068230012854028959.davem@davemloft.net>
To: ktkhai@virtuozzo.com
Cc: vyasevic@redhat.com, edumazet@google.com,
        nicolas.dichtel@6wind.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] Introduce rtnl_lock_killable()
From: David Miller <davem@davemloft.net>
In-Reply-To: <152105492788.24797.10467675660981296096.stgit@localhost.localdomain>
References: <152105492788.24797.10467675660981296096.stgit@localhost.localdomain>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Kirill Tkhai <ktkhai@virtuozzo.com>
Date: Wed, 14 Mar 2018 22:17:11 +0300

> rtnl_lock() is widely used mutex in kernel. Some of kernel code
> does memory allocations under it. In case of memory deficit this
> may invoke OOM killer, but the problem is a killed task can't
> exit if it's waiting for the mutex. This may be a reason of deadlock
> and panic.
> 
> This patchset adds a new primitive, which responds on SIGKILL,
> and it allows to use it in the places, where we don't want
> to sleep forever. Also, the first place is made to use it.

This looks reasonable.  Series applied, thank you.