netdev - Re: [PATCH net-next 0/2] Introduce rtnl_lock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20180316.123142.2068230012854028959.davem@davemloft.net>
Date:   Fri, 16 Mar 2018 12:31:42 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     ktkhai@...tuozzo.com
Cc:     vyasevic@...hat.com, edumazet@...gle.com,
        nicolas.dichtel@...nd.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/2] Introduce rtnl_lock_killable()

From: Kirill Tkhai <ktkhai@...tuozzo.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.