Received: by 10.213.65.68 with SMTP id h4csp3098098imn; Mon, 2 Apr 2018 21:40:19 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/fyGy74x2sFWVp6cB/ABM5M3q4LwdEpadp+6QjfbLhmfVh+MU6TvEglAzQOIBJrsOO+L+i X-Received: by 10.99.123.80 with SMTP id k16mr8130911pgn.173.1522730419088; Mon, 02 Apr 2018 21:40:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522730419; cv=none; d=google.com; s=arc-20160816; b=bkKCoksSnomWyP2tyOrEiWv/yXWr9ds+wT+KAM44Iws+XOvd7cxWS0sqRloOTQntr4 SlD6jWPl4dBQgrP2E6fEs96qRXz0pW7kC94l7sPJ+/e82xEUeCWTggU4/l3AyirAOAM1 6YpFfOPuYg6uY4ikeV/jAvTbncmJ+DBkT8pj4u4/xzBDc1EHHOm/hNRjJM5faO4ygXQf 1O60XYy9JOaTIz1DX2QNTQX3yQAburVJ5jdfmMmSZXWurWWcjRN2+1dCgPnjFeeOgwbi 1HwjOTbb7Yr03Y5v3Ssi5CvkqJ/O8Wr8pFBHecgN9KZtjxQQ3Y4xKFiR9D0Va2EWgqMs pVRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=m6BWjdg4kpxsRjfWryBjQhw84bZ2/+kfPQNHvdFA/Rg=; b=ISfEv+KSSA72g79fd/Nl9l2M2NzOUZ3L72oZVy81sixu40d4+uEo4AP0Mbh9gwcDD4 mcRcIM1PVeepd1dXfWhEAA2uyuXpOP8Ask1xuJuHnw04Y6svsKbb7S6kqnVebz491B9N wQQycsaJoZOm3usx/ysBVB6kyG5RKnj1R8UbIpgFk/AFutogpVql4C9UUe1Iz8nnlpgw 7NPbiiFAPLWx6O4L5AUYEZbacqtJH3z6wLCvUb0CsphW68MbSApaZe29HmRbVnDJU7dw /GNxFUJsV+hAt13znAeZFxKJzhQTmQacigbQpDoVOEpzVLG+xIe2vtnZPtsIz+v5B7Xi rMlQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m1si1509488pff.43.2018.04.02.21.40.05; Mon, 02 Apr 2018 21:40:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752777AbeDCEi7 (ORCPT + 99 others); Tue, 3 Apr 2018 00:38:59 -0400 Received: from ipmail06.adl6.internode.on.net ([150.101.137.145]:61046 "EHLO ipmail06.adl6.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750814AbeDCEi5 (ORCPT ); Tue, 3 Apr 2018 00:38:57 -0400 Received: from ppp59-167-129-252.static.internode.on.net (HELO dastard) ([59.167.129.252]) by ipmail06.adl6.internode.on.net with ESMTP; 03 Apr 2018 14:08:56 +0930 Received: from dave by dastard with local (Exim 4.80) (envelope-from ) id 1f3Dig-0004ib-Mp; Tue, 03 Apr 2018 14:38:54 +1000 Date: Tue, 3 Apr 2018 14:38:54 +1000 From: Dave Chinner To: syzbot Cc: darrick.wong@oracle.com, linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Re: WARNING: bad unlock balance in xfs_iunlock Message-ID: <20180403043854.GL1150@dastard> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 02, 2018 at 07:01:02PM -0700, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > 86bbbebac1933e6e95e8234c4f7d220c5ddd38bc (Mon Apr 2 18:47:07 2018 +0000) > Merge branch 'ras-core-for-linus' of > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip > syzbot dashboard link: > https://syzkaller.appspot.com/bug?extid=84a67953651a971809ba > > C reproducer: https://syzkaller.appspot.com/x/repro.c?id=5719304272084992 > syzkaller reproducer: > https://syzkaller.appspot.com/x/repro.syz?id=5767783983874048 What a mess. A hand built, hopelessly broken filesystem image made up of hex dumps, written into a mmap()d region of memory, then copied into a tmpfs file and mounted with the loop device. Engineers that can debug broken filesystems don't grow on trees. If we are to have any hope of understanding what the hell this test is doing, the bot needs to supply us with a copy of the built filesystem image the test uses. We need to be able to point forensic tools at the image to decode all the structures into human readable format - if we are forced to do that by hand or jump through hoops to create our own filesystem image than I'm certainly not going to waste time looking at these reports... Cheers, Dave. -- Dave Chinner david@fromorbit.com