Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp2042425imm; Fri, 6 Jul 2018 10:45:20 -0700 (PDT) X-Google-Smtp-Source: AAOMgpf0elMPfJYCx/PcXLR5aUVCcNKweViZ8kQ1brIx4tHkBonVCu5s/3bW8OOk9fM1FW4n7xlJ X-Received: by 2002:a62:2942:: with SMTP id p63-v6mr11550657pfp.62.1530899120827; Fri, 06 Jul 2018 10:45:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530899120; cv=none; d=google.com; s=arc-20160816; b=tsQG0xxE95YALocb+I7E31a0wycNdYGIEMuXyLPEPnCioDJRWbQWvw9YQ8qYILwxbf YEUbQKU5JuVPQh4TXInzTFd2GffuVzGpi2r7OFbpAm+BAZGcOLO30qfa4IdMctRd23By ef1nmKQQDd/0dfSENUKvwOJc2KTKz9pE8pfT6uPvIfDNQH53jT04eOkPJd6+26trNyb/ WKG2u6DhbEtBnkibklPXnsl8N0YjISoLKHtAv2e4YT+p3kLfl4GiBhwEc99LDeoqj0mA 99npthG9anKzUF/jSjq73E+G6zmxKZx1nxukD+ODDtQgtlvwuIM078DQ+dor9BKVJsGX yObA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:cc:to:from:date :arc-authentication-results; bh=p6d9x7EED88LZKUaAiFxdPe+odrF6c4rGK9Q9NsoQmk=; b=W5QvmiE50ynnJ7/8LDYhROG10+m+Pe61ScisnwYe6nS1e2hEMHSCKDyuEl6ljpciAO kYIsuOjEchmC5zJiKFlN0eXUI1lUiP9YnaLaNfJ+nZ829RTf1EvWnxwuu/soJ2YJjINI Ra799YeCbQ6+kMrMrkdI/avX82Xs66R46omHHd25pximCoR6RVmom4Tf0NlNHVdU/9iw jeAAwFLU3x7LhxRrnMQUxyMgrL8uhyCgRRfZ7F3o3Ark6PFcNDi9IVkzCz8vWvTrn4s1 bksjNXFEjTVpbFUFWfAVDFDJ3lG2XKUuibWiyqDK8OU8njx+U0NZYfHKCL8Kk6efqxZg ItUg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k72-v6si9096730pfj.141.2018.07.06.10.45.06; Fri, 06 Jul 2018 10:45:20 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933857AbeGFRn2 (ORCPT + 99 others); Fri, 6 Jul 2018 13:43:28 -0400 Received: from complete.lackof.org ([198.49.126.79]:36378 "EHLO complete.lackof.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933090AbeGFRn0 (ORCPT ); Fri, 6 Jul 2018 13:43:26 -0400 Received: from localhost (c-73-78-137-212.hsd1.co.comcast.net [73.78.137.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by complete.lackof.org (Postfix) with ESMTPSA id AE66533E006A; Fri, 6 Jul 2018 11:43:24 -0600 (MDT) Date: Fri, 6 Jul 2018 11:43:24 -0600 From: dann frazier To: Theodore Ts'o , linux-ext4@vger.kernel.org Cc: linux-kernel@vger.kernel.org, yanaijie@huawei.com, colin.king@canonical.com, kamal.mostafa@canonical.com, ike.pan@canonical.com Subject: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap Message-ID: <20180706174324.GA3049@xps13.dannf> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-Virus-Scanned: clamav-milter 0.100.0 at complete.lackof.org X-Virus-Status: Clean X-Spam-Status: No, score=0.3 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on complete.lackof.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, We're seeing a regression triggered by the stress-ng[*] "chdir" test that I've bisected to: 044e6e3d74a3 ext4: don't update checksum of new initialized bitmaps So far we've only seen failures on servers based on HiSilicon's family of ARM64 SoCs (D05/Hi1616 SoC, D06/Hi1620 SoC). On these systems it is very reproducible. = Test Case = #!/bin/sh umount /tmp/mnt || /bin/true mkdir -p /tmp/mnt mkfs.ext4 -F /dev/sda1 mount /dev/sda1 /tmp/mnt # Running directly under /tmp/mnt doesn't trigger the issue, we need # this subdirectory for some reason dir="/tmp/mnt/tmp/disk_stress_ng_f70f0f26-b332-4c48-9e07-67c529770e3d" mkdir -p "$dir" stress-ng --aggressive --verify --timeout 240 --temp-path "$dir" \ --chdir 0 --hdd-opts dsync --readahead-bytes 16M -k = Result = [70586.263840] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [70586.637085] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap - block_group = 43936, inode_bitmap = 1439694864 [70602.296551] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap - block_group = 48896, inode_bitmap = 1602224144 [70602.409291] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap - block_group = 48928, inode_bitmap = 1603272720 Full dmesg: http://people.canonical.com/~dannf/d05-stress-ng/d05-sas-chdir-4.18.0-rc3+.dmesg [*] http://kernel.ubuntu.com/~cking/stress-ng/