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] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 23 Aug 2014 11:19:24 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jon.maloy@...csson.com
Cc:	netdev@...r.kernel.org, paul.gortmaker@...driver.com,
	erik.hugne@...csson.com, ying.xue@...driver.com, maloy@...jonn.com,
	tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH net-next 00/17] tipc: Merge port and socket layer code

From: Jon Maloy <jon.maloy@...csson.com>
Date: Fri, 22 Aug 2014 18:09:03 -0400

> After the removal of the TIPC native interface, there is no reason to
> keep a distinction between a "generic" port layer and a "specific"
> socket layer in the code. Throughout the last months, we have posted
> several series that aimed at facilitating removal of the port layer,
> and in particular the port_lock spinlock, which in reality duplicates
> the role normally kept by lock_sock()/bh_lock_sock().
> 
> In this series, we finalize this work, by making a significant number of
> changes to the link, node, port and socket code, all with the aim of
> reducing dependencies between the layers. In the final commits, we then
> remove the port spinlock, port.c and port.h altogether.
> 
> After this series, we have a socket layer that has only few dependencies
> to the rest of the stack, so that it should be possible to continue
> cleanups of its code without significantly affecting other code.

Series applied, thanks Jon.

> It should be noted that commit ##1 and 2 are already in 'net' 
> (ac32c7f705692b92fe12dcbe88fe87136fdfff6f and 
> 02784f1b05b8f241c8180af88869e717e2758593), but not yet in net-next.
> Since they are prerequisites for the rest of the series to apply, I
> prepend them to the series.

I decided to handle this by merging 'net' into 'net-next' and then
just skipping those first two patches in the series.  Thanks for
letting me know about this dependency.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ