Date: Thu, 14 Apr 2011 09:04:57 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: FreeBSD virtualization mailing list <freebsd-virtualization@FreeBSD.org> Cc: FreeBSD stable mailing list <freebsd-stable@FreeBSD.org> Subject: HEADS UP: will merge VNET socket push back changes to stable/8 Message-ID: <20110414090222.O3039@maildrop.int.zabbadoz.net>
next in thread | raw e-mail | index | archive | help
Hi,
this is a heads up in case anyone is relying on this in private VNET
modules or code. I am planning on merging this code to stable/8
probably during the weekend. It should be a NOP for almost everyone,
especially if not running a VIMAGE kernel.
/bz
--
Bjoern A. Zeeb You have to have visions!
Stop bit received. Insert coin for new address family.
---------- Forwarded message ----------
Date: Wed, 16 Feb 2011 21:29:14 +0000 (UTC)
From: Bjoern A. Zeeb <bz@FreeBSD.org>
To: src-committers@freebsd.org, svn-src-all@freebsd.org,
svn-src-head@freebsd.org
Subject: svn commit: r218757 - in head/sys: fs/nfsclient fs/portalfs kern net
netgraph/bluetooth/socket netinet nfsclient rpc
Author: bz
Date: Wed Feb 16 21:29:13 2011
New Revision: 218757
URL: http://svn.freebsd.org/changeset/base/218757
Log:
Mfp4 CH=177274,177280,177284-177285,177297,177324-177325
VNET socket push back:
try to minimize the number of places where we have to switch vnets
and narrow down the time we stay switched. Add assertions to the
socket code to catch possibly unset vnets as seen in r204147.
While this reduces the number of vnet recursion in some places like
NFS, POSIX local sockets and some netgraph, .. recursions are
impossible to fix.
The current expectations are documented at the beginning of
uipc_socket.c along with the other information there.
Sponsored by: The FreeBSD Foundation
Sponsored by: CK Software GmbH
Reviewed by: jhb
Tested by: zec
Tested by: Mikolaj Golub (to.my.trociny gmail.com)
MFC after: 2 weeks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110414090222.O3039>