netdev - [PATCH net-next 0/7] tipc: some link level code improvements

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-next>] [day] [month] [year] [list]

Message-Id: <1444935166-12745-1-git-send-email-jon.maloy@ericsson.com>
Date:	Thu, 15 Oct 2015 14:52:39 -0400
From:	Jon Maloy <jon.maloy@...csson.com>
To:	davem@...emloft.net
Cc:	netdev@...r.kernel.org,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	parthasarathy.xx.bhuvaragan@...csson.com,
	richard.alpe@...csson.com, ying.xue@...driver.com,
	maloy@...jonn.com, tipc-discussion@...ts.sourceforge.net,
	Jon Maloy <jon.maloy@...csson.com>
Subject: [PATCH net-next 0/7] tipc: some link level code improvements

Extensive testing has revealed some weaknesses and non-optimal solutions
in the link level code.

This commit series addresses those issues.


Jon Maloy (7):
  tipc: limit usage of temporary skb list during packet reception
  tipc: simplify tipc_link_rcv() reception loop
  tipc: improve sequence number checking
  tipc: disallow packet duplicates in link deferred queue
  tipc: delay ESTABLISH state event when link is established
  tipc: send out RESET immediately when link goes down
  tipc: update node FSM when peer RESET message is received

 net/tipc/bearer.c    |   8 +--
 net/tipc/link.c      | 170 ++++++++++++++++++++++++++++++---------------------
 net/tipc/link.h      |   5 +-
 net/tipc/msg.c       |  31 ++++++++++
 net/tipc/msg.h       |  34 +----------
 net/tipc/node.c      |  43 +++++++++----
 net/tipc/udp_media.c |   1 -
 7 files changed, 172 insertions(+), 120 deletions(-)

-- 
1.9.1

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