From owner-freebsd-fs@FreeBSD.ORG  Wed Nov  7 15:15:42 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 8699A626
 for <freebsd-fs@freebsd.org>; Wed,  7 Nov 2012 15:15:42 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 by mx1.freebsd.org (Postfix) with ESMTP id E28468FC0A
 for <freebsd-fs@freebsd.org>; Wed,  7 Nov 2012 15:15:41 +0000 (UTC)
Received: from tom.home (localhost [127.0.0.1])
 by kib.kiev.ua (8.14.5/8.14.5) with ESMTP id qA7FFZHw065378;
 Wed, 7 Nov 2012 17:15:35 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
X-DKIM: OpenDKIM Filter v2.5.2 kib.kiev.ua qA7FFZHw065378
Received: (from kostik@localhost)
 by tom.home (8.14.5/8.14.5/Submit) id qA7FFY2R065377;
 Wed, 7 Nov 2012 17:15:34 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Wed, 7 Nov 2012 17:15:34 +0200
From: Konstantin Belousov <kostikbel@gmail.com>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Subject: Re: will non-MPSAFE-deorbit remove MNTK_MPSAFE?
Message-ID: <20121107151534.GR73505@kib.kiev.ua>
References: <alpine.GSO.1.10.1211071001040.2164@multics.mit.edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="i9pGKxSHTiGLjQSm"
Content-Disposition: inline
In-Reply-To: <alpine.GSO.1.10.1211071001040.2164@multics.mit.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Spam-Status: No, score=0.2 required=5.0 tests=ALL_TRUSTED,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 version=3.3.2
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 15:15:42 -0000


--i9pGKxSHTiGLjQSm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 07, 2012 at 10:01:21AM -0500, Benjamin Kaduk wrote:
> Per the thread on svn-src-head, I was wondering if there are plans to=20
> remove the MNTK_MPSAFE flag at some point.
> A quick grep through the sources seems to indicate that it is not really=
=20
> used, as the check in VFS_NEEDSGIANT was removed in r241896.
Yes, it will be removed some time before 10.0.
Right now I opted to not change mpsafe filesystem modules.

An option was to keep the code which refused to mount filesystem
without MNTK_MPSAFE set, but I decided to cut the whole tail once.
But I did not wanted to touch working mpsafe filesystems, thus
MNTK_MPSAFE survived yet.

--i9pGKxSHTiGLjQSm
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlCaexYACgkQC3+MBN1Mb4iXbQCgl/foIv1y4q6ilOt8TY632aOV
lCEAnjU/Sah4fvQfGWxdgwFUp7HXtOpH
=eSlz
-----END PGP SIGNATURE-----

--i9pGKxSHTiGLjQSm--