From owner-freebsd-current@FreeBSD.ORG Thu Feb 23 20:20:38 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B007D106566B; Thu, 23 Feb 2012 20:20:38 +0000 (UTC) (envelope-from flo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9826B8FC18; Thu, 23 Feb 2012 20:20:38 +0000 (UTC) Received: from nibbler-wlan.fritz.box (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1NKKaZH019393; Thu, 23 Feb 2012 20:20:37 GMT (envelope-from flo@FreeBSD.org) Message-ID: <4F469F94.5080606@FreeBSD.org> Date: Thu, 23 Feb 2012 21:20:36 +0100 From: Florian Smeets User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120216 Thunderbird/11.0 MIME-Version: 1.0 To: Gleb Kurtsou References: <4F358F01.1090508@FreeBSD.org> <20120211102006.GA1274@reks> In-Reply-To: <20120211102006.GA1274@reks> X-Enigmail-Version: 1.4a1pre Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig33C98DBE6BD456685B857AFF" Cc: decke@FreeBSD.org, Konstantin Belousov , "current@freebsd.org" Subject: Re: Processes getting stuck in state tmpfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2012 20:20:38 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig33C98DBE6BD456685B857AFF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 11.02.12 11:20, Gleb Kurtsou wrote: > On (10/02/2012 22:41), Florian Smeets wrote: >> Hi, >> >> if you set WRKDIRPREFIX to a tmpfs mountpoint and try to build audio/g= sm >> from ports one of the mv processes gets stuck in state tmpfs quite >> often. Traces from a kernel with WITTNESS and DEBUG_VFS_LOCKS are >> available here http://tb.smeets.im/~flo/tmpfs.txt >=20 > It's because of incorrect vnode locking order in tmpfs_rename. Issue is= > known and tmpfs is not the only file system suffering from it (e.g. ext= 2). >=20 > There two ways of working around it in tree: > * UFS: try locking vnode, unlock all vnodes on failure, restart, > relookup vnodes needed. > * ZFS: introduce directory entry locks to guarantee fvp won't disappear= , > fdvp can be safely traversed, etc. That won't be easy.. >=20 > UFS-way would be a good temporal solution, but I think we should work o= n > improving VOP_RENAME() in a long run. >=20 > I'll try to prepare a patch in several days. >=20 Hey Gleb, did you get anywhere with this? Thanks, Florian --------------enig33C98DBE6BD456685B857AFF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk9Gn5QACgkQapo8P8lCvwkdwwCcDGIrgauqan48tjJ9LJoTGYOb q/QAnj+38Vh72Pt4hf+cPxHAEywIGC9F =lIx5 -----END PGP SIGNATURE----- --------------enig33C98DBE6BD456685B857AFF--