Date: Wed, 29 Feb 2012 23:44:47 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Mikolaj Golub <trociny@freebsd.org>, John Baldwin <jhb@freebsd.org>, Konstantin Belousov <kib@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r232317 - in head: . sys/kern sys/sys Message-ID: <14D2BDEC-B9C7-4B2D-AF2C-60598CCE1EBF@lists.zabbadoz.net> In-Reply-To: <201202292138.q1TLcVFv046104@svn.freebsd.org> References: <201202292138.q1TLcVFv046104@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29. Feb 2012, at 21:38 , Mikolaj Golub wrote: > Author: trociny > Date: Wed Feb 29 21:38:31 2012 > New Revision: 232317 > URL: http://svn.freebsd.org/changeset/base/232317 >=20 > Log: > Introduce VOP_UNP_BIND(), VOP_UNP_CONNECT(), and VOP_UNP_DETACH() > operations for setting and accessing vnode's v_socket field. >=20 > The operations are necessary to implement proper unix socket handling > on layered file systems like nullfs(5). >=20 > This change fixes the long standing issue with nullfs(5) being in = that > unix sockets did not work between lower and upper layers: if we bound > to a socket on the lower layer we could connect only to the lower > path; if we bound to the upper layer we could connect only to the > upper path. The new behavior is one can connect to both the lower and > the upper paths regardless what layer path one binds to. At this point I wonder if jhb has added (enough) spares with an earlier = MFC of another change or whether we'll break thing again? >=20 > PR: kern/51583, kern/159663 > Suggested by: kib > Reviewed by: arch > MFC after: 2 weeks --=20 Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14D2BDEC-B9C7-4B2D-AF2C-60598CCE1EBF>