From owner-freebsd-fs@FreeBSD.ORG Thu Dec 13 12:29:26 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D6DDB7; Thu, 13 Dec 2012 12:29:26 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 61BCC8FC08; Thu, 13 Dec 2012 12:29:25 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id je9so986444bkc.13 for ; Thu, 13 Dec 2012 04:29:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=D1UYFwr8ACvDOt8LYE2rEHeZQDRe9ontGpWFGB6DvM4=; b=vYOW5y5TpUEaDHA1O5VjOLgFYLqfkwrDz9tF8IXEP4NWlGCn6RybjGQVGQmCU5FYCp zeIEQOMhMXlwbPLs/lY8sLZeI1xulDC30bshKwQg6jszBS86ImiA7CSI5j3YQklWqFGi H7yhwh1DCuFYJxTFFSMKB26feoXo0yvq8OpqhODj4COjs79VtgfM5Z6xg96IxCsnib7l yYXtEvhgQJL37HbsMtYVhdH++itVM2D2evmFKySmNPBtXeX9O8DKYmNMAJLFyr3ldQHu pzeov3w316igGrdgra9ZH3Dj94CZsm1VhDZoF/yRuAS5bM4CXEJ0QHJ7lUS5ich6sT9i 2/Uw== Received: by 10.204.6.87 with SMTP id 23mr905559bky.78.1355401764304; Thu, 13 Dec 2012 04:29:24 -0800 (PST) Received: from [192.168.1.129] ([91.196.229.122]) by mx.google.com with ESMTPS id u3sm1182439bkw.9.2012.12.13.04.29.21 (version=SSLv3 cipher=OTHER); Thu, 13 Dec 2012 04:29:22 -0800 (PST) Message-ID: <50C9CA1C.8030002@gmail.com> Date: Thu, 13 Dec 2012 14:29:16 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20100101 Firefox/17.0 SeaMonkey/2.14.1 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: clang compiled kernel panic when mounting zfs root on i386 References: <50b37d46.8584440a.735c.ffffb4e6@mx.google.com> <20121126171658.GD3013@kib.kiev.ua> <20121127071243.D1255@besplex.bde.org> <20121129232944.GQ3013@kib.kiev.ua> <50b8a9c5.e64dec0a.1d88.133a@mx.google.com> <20121130164715.GW3013@kib.kiev.ua> <50b9cf0c.0fd9650a.5bbf.ffffb9b3@mx.google.com> <20121203224132.GJ3013@kib.kiev.ua> <50C880D7.1040907@gmail.com> <50C8DC8E.1080204@FreeBSD.org> In-Reply-To: <50C8DC8E.1080204@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2012 12:29:26 -0000 12.12.2012 21:35, Dimitry Andric: > On 2012-12-12 14:04, Volodymyr Kostyrko wrote: >> 04.12.2012 00:41, Konstantin Belousov: >>> Please try the patch below. It might give an immediate relief, but still >>> there are many offenders in the backtrace. >> >> I'm having almost the same issue and the patch doesn't work for me. > ... > > Looking at the stack frame addresses, it seems some of them are mangled. > Did you type this by hand? The differences between subsequent frames > are a bit strange because of it (and because of awk's integer > processing): Yes, I had typed that by hand. I attached link to the pictures just in case. > The kernel stack is just 8,192 bytes; since you can see these routines > are all consuming massive amounts of stack, and the calls are very > deeply nested, it is almost inevitable that it would crash. > > Especially the recursive spa_load and traverse_visitbp calls are scary, > because that can grow out of hand very quickly. It is probably tricky > to remove the recursion... After playing more with this kernel I also found it can crash not only by this scenario. There are different possible ways. I actually don't think there's a point fixing it right now. New clang is coming anyway... -- Sphinx of black quartz, judge my vow.