netdev - Re: [PATCH net-next v3 0/6] tipc: refcount and memory leak fixes

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

Message-Id: <20140306.144714.915091981153232193.davem@davemloft.net>
Date:	Thu, 06 Mar 2014 14:47:14 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	erik.hugne@...csson.com
Cc:	netdev@...r.kernel.org, tipc-discussion@...ts.sourceforge.net,
	jon.maloy@...csson.com, maloy@...jonn.com, ying.xue@...driver.com,
	paul.gortmaker@...driver.com, richard.alpe@...csson.com
Subject: Re: [PATCH net-next v3 0/6] tipc: refcount and memory leak fixes

From: <erik.hugne@...csson.com>
Date: Thu, 6 Mar 2014 14:40:15 +0100

> v3: Remove error logging from data path completely. Rebased on top of
>     latest net merge.
> 
> v2: Drop specific -ENOMEM logging in patch #1 (tipc: allow connection
>     shutdown callback to be invoked in advance) And add a general error
>     message if an internal server tries to send a message on a
>     closed/nonexisting connection.
> 
> In addition to the fix for refcount leak and memory leak during
> module removal, we also fix a problem where the topology server
> listening socket where unexpectedly closed. We also eliminate an
> unnecessary context switch during accept()/recvmsg() for nonblocking
> sockets.
> 
> It might be good to include this patchset in stable aswell. After the 
> v3 rebase on latest merge from net all patches apply cleanly on that
> tree.

Series applied and queued up for -stable, 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