netdev - [PATCH net 0/2] tipc: clean up components initialization code

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 20 Feb 2014 11:32:48 +0800
From:	Ying Xue <ying.xue@...driver.com>
To:	<davem@...emloft.net>
CC:	<jon.maloy@...csson.com>, <Paul.Gortmaker@...driver.com>,
	<erik.hugne@...csson.com>, <netdev@...r.kernel.org>,
	<tipc-discussion@...ts.sourceforge.net>, <wangweidong1@...wei.com>
Subject: [PATCH net 0/2] tipc: clean up components initialization code

In this series, we will fix a regression issue involved by commit
6e967adf7(tipc: relocate common functions from media to bearer)
But before the issue is fixed, we firstly adjust the process of
components initialization so as to remove all enabled flags from
necessary tipc components. Otherwise, without the change, we also
have to add an extra enabled flag into bearer layer indicating
whether bearer setup is finshed or not.

Ying Xue (2):
  tipc: remove all enabled flags from all tipc components
  tipc: make bearer set up in module insertion stage

 net/tipc/bearer.c     |    7 +++-
 net/tipc/config.c     |    2 +-
 net/tipc/core.c       |  109 ++++++++++++++++++++++++++-----------------------
 net/tipc/core.h       |    1 -
 net/tipc/name_table.c |    3 --
 net/tipc/netlink.c    |    8 ----
 net/tipc/ref.c        |    3 --
 net/tipc/server.c     |    5 ---
 net/tipc/server.h     |    2 -
 net/tipc/socket.c     |    8 ----
 10 files changed, 66 insertions(+), 82 deletions(-)

-- 
1.7.9.5

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