netdev - [PATCH 0/9 net-next-2.6] [TIPC]: System & debug output modifications

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]

Date:	Mon, 28 Apr 2008 15:48:37 -0400
From:	Allan Stephens <allan.stephens@...driver.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, allan.stephens@...driver.com
Subject: [PATCH 0/9 net-next-2.6] [TIPC]: System & debug output modifications


This patch set includes a number of fixes and cleanups for the code TIPC
uses to print its system and debug output. Please see each individual patch
for further description.

Summary:

 net/tipc/config.c     |    2 
 net/tipc/core.c       |    6 +
 net/tipc/core.h       |  124 ++++++++++++++++----------
 net/tipc/dbg.c        |  231 ++++++++++++++++++++++++-------------------------
 net/tipc/dbg.h        |   12 +--
 net/tipc/link.c       |   20 +++-
 net/tipc/msg.c        |   10 +-
 net/tipc/name_distr.c |    3 -
 8 files changed, 218 insertions(+), 190 deletions(-)

Allan Stephens (9):
      [TIPC]: Simplify log buffer resizing
      [TIPC]: Provide feedback when log buffer resizing fails
      [TIPC]: Fix recursive spinlock invocation in print buffer code
      [TIPC]: Fix null pointer dereference in debug code
      [TIPC]: Elimination of print buffer chaining
      [TIPC]: Cosmetic cleanup of print buffer code
      [TIPC]: Cosmetic cleanup of system & debug output declarations
      [TIPC]: Exclude debug-only print buffer code when not debugging
      [TIPC]: Update version number to TIPC 1.6.4

Thanks,
Al
--
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