From owner-freebsd-stable@freebsd.org Fri Jul 22 20:02:08 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 250E4BA293F for ; Fri, 22 Jul 2016 20:02:08 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 668A91B63 for ; Fri, 22 Jul 2016 20:02:06 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA02371; Fri, 22 Jul 2016 23:01:57 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bQgdx-00073y-Md; Fri, 22 Jul 2016 23:01:57 +0300 Subject: Re: Panic on BETA1 in the ZFS subsystem To: Steven Hartland , Karl Denninger , freebsd-stable@FreeBSD.org References: <8f44bc09-1237-44d0-fe7a-7eb9cf4fe85b@denninger.net> <54e5974c-312e-c33c-ab83-9e1148618ddc@FreeBSD.org> <97cf5283-683b-83fd-c484-18c14973b065@denninger.net> <1f064549-fa72-fe9b-d66d-85923437bb9b@denninger.net> <6cb46059-85c8-0c3b-7346-773647f1a962@FreeBSD.org> <89b66fd6-09d8-d8a2-4894-3a6e5f73a0bb@multiplay.co.uk> From: Andriy Gapon Message-ID: <0b541107-13cb-f683-fae0-2055d85d5b22@FreeBSD.org> Date: Fri, 22 Jul 2016 23:01:02 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <89b66fd6-09d8-d8a2-4894-3a6e5f73a0bb@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 20:02:08 -0000 On 22/07/2016 16:39, Steven Hartland wrote: > Yes does indeed sound like what happened to me. Can you think of any way that we can use to limit the zio_execute chaining? Like somehow keeping track of the nesting and returning NULL instead of a queued zio when we reach a limit. -- Andriy Gapon