netdev - Re: [PATCH net-next 00/10] purge signal handler infrastructure

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 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]

Date:	Mon, 05 May 2014 17:27:10 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	ying.xue@...driver.com
Cc:	jon.maloy@...csson.com, Paul.Gortmaker@...driver.com,
	erik.hugne@...csson.com, netdev@...r.kernel.org,
	tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH net-next 00/10] purge signal handler infrastructure

From: Ying Xue <ying.xue@...driver.com>
Date: Mon, 5 May 2014 08:56:08 +0800

> When we delay some actions to be executed in asynchronous contexts,
> these usually add unnecessary code complexities, and make their
> behaviours unpredictable and indeterministic. Moreover, as the signal
> handler infrastructure is first stopped when tipc module is removed,
> this may cause some potential risks for us. For instance, although
> signal handler is already stopped, some tipc components still submit
> signal requests to signal handler infrastructure, which may lead to
> some resources not to be released or freed correctly.
> 
> So the series aims to convert all actions being performed in tasklet
> context asynchronously with interface provided by signal handler
> infrastructure to be executed synchronously, thereby deleting the
> whole infrastructure of signal handler.

Series applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html