From owner-freebsd-current@freebsd.org Sun May 27 19:42:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA297F7E29E for ; Sun, 27 May 2018 19:42:02 +0000 (UTC) (envelope-from kp@krion.cc) Received: from krion.cc (krion.cc [148.251.235.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 683CA6B1F3 for ; Sun, 27 May 2018 19:42:02 +0000 (UTC) (envelope-from kp@krion.cc) Received: from jo (90-152-149-189.static.highway.a1.net [90.152.149.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by krion.cc (Postfix) with ESMTPSA id 9BD701EB1F; Sun, 27 May 2018 21:42:00 +0200 (CEST) Date: Sun, 27 May 2018 21:41:59 +0200 From: Kirill Ponomarev To: Slawa Olhovchenkov Cc: Alexander Leidinger , freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS Message-ID: <20180527194159.v54ox3vlthpuvx4q@jo> References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> <20180522144055.GD1954@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ptgiukr3w63nhqco" Content-Disposition: inline In-Reply-To: <20180522144055.GD1954@zxy.spb.ru> User-Agent: NeoMutt/20180512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sun, 27 May 2018 19:42:03 -0000 --ptgiukr3w63nhqco Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 05/22, Slawa Olhovchenkov wrote: > > It has been a while since I tried Karl's patch the last time, and I =20 > > stopped because it didn't apply to -current anymore at some point. > > Will what is provided right now in the patch work on -current? >=20 > I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g > I am don't know how to have two distinct patch (for stable and current) i= n one review. =20 I'm experiencing these issues sporadically as well, would you mind to publish this patch for fresh current? --ptgiukr3w63nhqco Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFdBAABCABHFiEEJCHRFhEAQujKni1pDyI9/LMCykUFAlsLCgcpFIAAAAAAFQAL cGthLWFkZHJlc3NAZ251cGcub3Jna3BAa3Jpb24uY2MACgkQDyI9/LMCykUiPQf+ Lssi/ksaBHOd9qcW+tEwc4b8+U4L+CGhyw+Eghq74f99LztEoWXE0sXrdgPP7a8R HTUmBjXoP5115r4IXTb3MtLMd7xSuF6IZXr6Bi8V+nIgcZ3p4dQDo6SYhj/ygWJn 0dI9kw0OAAgSUZNSEWtXzPAji/H9Rt/7PhimI1WtURzNctB5DsbvmXjDHOJdob2i tqo1GTic2/Ki6hDzAmU97or8AnsjNvOqvcwBxHQ1IS2yKH+SyRg5uKubK8w6KoqK SYPjGSSpQigQDWoTPK2KE0Sjn28OLpfYOoxw0bScq6tvZOZoieOy+qMZOV0EIN/5 Blsf/YH2EruTa30BiEplVg== =uP1A -----END PGP SIGNATURE----- --ptgiukr3w63nhqco--