From: David Miller <davem@davemloft.net>
To: ying.xue@windriver.com
Cc: jon.maloy@ericsson.com, Paul.Gortmaker@windriver.com,
erik.hugne@ericsson.com, netdev@vger.kernel.org,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH net-next 00/10] purge signal handler infrastructure
Date: Mon, 05 May 2014 17:27:10 -0400 (EDT) [thread overview]
Message-ID: <20140505.172710.1571847590302532388.davem@davemloft.net> (raw)
In-Reply-To: <1399251378-23842-1-git-send-email-ying.xue@windriver.com>
From: Ying Xue <ying.xue@windriver.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.
prev parent reply other threads:[~2014-05-05 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 0:56 [PATCH net-next 00/10] purge signal handler infrastructure Ying Xue
2014-05-05 0:56 ` [PATCH net-next 01/10] tipc: always use tipc_node_lock() to hold node lock Ying Xue
2014-05-05 0:56 ` [PATCH net-next 02/10] tipc: adjust order of variables in tipc_node structure Ying Xue
2014-05-05 0:56 ` [PATCH net-next 03/10] tipc: rename setup_blocked variable of node struct to flags Ying Xue
2014-05-05 0:56 ` [PATCH net-next 04/10] tipc: avoid to asynchronously notify subscriptions Ying Xue
2014-05-05 0:56 ` [PATCH net-next 05/10] tipc: remove TIPC_NAMES_GONE node flag Ying Xue
2014-05-05 0:56 ` [PATCH net-next 06/10] tipc: avoid to asynchronously deliver name tables to peer node Ying Xue
2014-05-05 0:56 ` [PATCH net-next 07/10] tipc: define new functions to operate bc_lock Ying Xue
2014-05-05 0:56 ` [PATCH net-next 08/10] tipc: convert allocations of global variables associated with bclink Ying Xue
2014-05-05 0:56 ` [PATCH net-next 09/10] tipc: avoid to asynchronously reset all links Ying Xue
2014-05-05 0:56 ` [PATCH net-next 10/10] tipc: purge signal handler infrastructure Ying Xue
2014-05-05 21:27 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140505.172710.1571847590302532388.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Paul.Gortmaker@windriver.com \
--cc=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).