Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp2077748ybp; Thu, 10 Oct 2019 01:47:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqxJ19U4CLc90W/OEj4JysPBfeNowjdjGi9B8+N2szIWoAYkOg6aAlawxI7W9lYVVZGMLRi6 X-Received: by 2002:a17:906:e2c4:: with SMTP id gr4mr6961126ejb.89.1570697237203; Thu, 10 Oct 2019 01:47:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570697237; cv=none; d=google.com; s=arc-20160816; b=Ysh2MrPDouImXX9SZCC31vCqQpOhjHIdG6V7VqTLU87r3zH5bTDNljW0gIjVonltJm MZ6iH7IE3uxLleAxKu9VqEmBkJJ9viJddiBK9tCKvHPpyfzdZ4wW+OD5SwTzzQ3/iO8c NcIeyC9Mm5PpxXvshWc8XnGyPshpfbl6mKoel25qFd049Vk9EmVVDVNVHxyhMZf+AVff 6lvq+W7hzttg5fjDut1bgLIDAatSUZhJzab6Sfmoiz2VVMpTocSBSlqZdD+QCPrYueYL 4F7dkrgO2Czkjc+vXaq9t/h9GtaeU+WsL1Yo+ksrY1XWbDxCgKhwk2cJq6KgmhjOpu/O TICQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=w2l/N5y7m9jTmnQtGg2uAAXjZ1A/a9mCupLDH+Y3HUo=; b=iD7QUQf3qR9eaVyR+Dhm5VVEZJA4qeRlcW2kdesQF06omzg7ZP8I9BZ8qJGRJdWAPX a9QqKfDvUsrz/Y+57BmXALYFbxGgTQtRuVjIZnPQu4Mz/jbTnM2Rk+Ebt7jEEpBSTx0X dcnBqRI38Z+x1nCj1g0baFpuj9j5pi4lAlhXnIM4kF+1UJo3/IRqfM4ablXDmYEjBhbb 9tQr1sahj9IQZL7qRMBHb9I3MjI3cqXi+ya/FuEQIGoOEq9TV0x3vcMHqc7x0+CcsA4I w0smd8oqWsP9qfszGThbKh+SJf6JbBPBj24zIvpgcSS1eHBQOBA2uKw5PCW0M+uNPah3 /ldw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=jWhzIzN0; 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 be24si2849194edb.120.2019.10.10.01.46.53; Thu, 10 Oct 2019 01:47:17 -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; dkim=pass header.i=@kernel.org header.s=default header.b=jWhzIzN0; 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 S2388109AbfJJInh (ORCPT + 99 others); Thu, 10 Oct 2019 04:43:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:48386 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388113AbfJJIne (ORCPT ); Thu, 10 Oct 2019 04:43:34 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 68E6721D56; Thu, 10 Oct 2019 08:43:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570697012; bh=NAi1+Bo0JVBgckqyAVTISXOYMwHPgSPKdbHxAFeiRps=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=jWhzIzN04N+klaDBL5JXnDDAJmA0dXmMphJHORUt9Ua2iqrYJ+5R1UfHwGujz7v1N EjsBOsfwEAvKVx7vD8F0pQ0A/akxhIWyLrQisliDCjb0HhGDCuoRmR5aBFbqqn/RtY HPzMX8m/++E3oQcYRdEZkAqoWceW0yDZvf9pr/8U= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Filipe Manana , Qu Wenruo , David Sterba , Sasha Levin Subject: [PATCH 5.3 136/148] Btrfs: fix selftests failure due to uninitialized i_mode in test inodes Date: Thu, 10 Oct 2019 10:36:37 +0200 Message-Id: <20191010083620.606605887@linuxfoundation.org> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20191010083609.660878383@linuxfoundation.org> References: <20191010083609.660878383@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Filipe Manana [ Upstream commit 9f7fec0ba89108b9385f1b9fb167861224912a4a ] Some of the self tests create a test inode, setup some extents and then do calls to btrfs_get_extent() to test that the corresponding extent maps exist and are correct. However btrfs_get_extent(), since the 5.2 merge window, now errors out when it finds a regular or prealloc extent for an inode that does not correspond to a regular file (its ->i_mode is not S_IFREG). This causes the self tests to fail sometimes, specially when KASAN, slub_debug and page poisoning are enabled: $ modprobe btrfs modprobe: ERROR: could not insert 'btrfs': Invalid argument $ dmesg [ 9414.691648] Btrfs loaded, crc32c=crc32c-intel, debug=on, assert=on, integrity-checker=on, ref-verify=on [ 9414.692655] BTRFS: selftest: sectorsize: 4096 nodesize: 4096 [ 9414.692658] BTRFS: selftest: running btrfs free space cache tests [ 9414.692918] BTRFS: selftest: running extent only tests [ 9414.693061] BTRFS: selftest: running bitmap only tests [ 9414.693366] BTRFS: selftest: running bitmap and extent tests [ 9414.696455] BTRFS: selftest: running space stealing from bitmap to extent tests [ 9414.697131] BTRFS: selftest: running extent buffer operation tests [ 9414.697133] BTRFS: selftest: running btrfs_split_item tests [ 9414.697564] BTRFS: selftest: running extent I/O tests [ 9414.697583] BTRFS: selftest: running find delalloc tests [ 9415.081125] BTRFS: selftest: running find_first_clear_extent_bit test [ 9415.081278] BTRFS: selftest: running extent buffer bitmap tests [ 9415.124192] BTRFS: selftest: running inode tests [ 9415.124195] BTRFS: selftest: running btrfs_get_extent tests [ 9415.127909] BTRFS: selftest: running hole first btrfs_get_extent test [ 9415.128343] BTRFS critical (device (efault)): regular/prealloc extent found for non-regular inode 256 [ 9415.131428] BTRFS: selftest: fs/btrfs/tests/inode-tests.c:904 expected a real extent, got 0 This happens because the test inodes are created without ever initializing the i_mode field of the inode, and neither VFS's new_inode() nor the btrfs callback btrfs_alloc_inode() initialize the i_mode. Initialization of the i_mode is done through the various callbacks used by the VFS to create new inodes (regular files, directories, symlinks, tmpfiles, etc), which all call btrfs_new_inode() which in turn calls inode_init_owner(), which sets the inode's i_mode. Since the tests only uses new_inode() to create the test inodes, the i_mode was never initialized. This always happens on a VM I used with kasan, slub_debug and many other debug facilities enabled. It also happened to someone who reported this on bugzilla (on a 5.3-rc). Fix this by setting i_mode to S_IFREG at btrfs_new_test_inode(). Fixes: 6bf9e4bd6a2778 ("btrfs: inode: Verify inode mode to avoid NULL pointer dereference") Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204397 Signed-off-by: Filipe Manana Reviewed-by: Qu Wenruo Signed-off-by: David Sterba Signed-off-by: Sasha Levin --- fs/btrfs/tests/btrfs-tests.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/fs/btrfs/tests/btrfs-tests.c b/fs/btrfs/tests/btrfs-tests.c index 1e3ba49493995..814a918998ece 100644 --- a/fs/btrfs/tests/btrfs-tests.c +++ b/fs/btrfs/tests/btrfs-tests.c @@ -51,7 +51,13 @@ static struct file_system_type test_type = { struct inode *btrfs_new_test_inode(void) { - return new_inode(test_mnt->mnt_sb); + struct inode *inode; + + inode = new_inode(test_mnt->mnt_sb); + if (inode) + inode_init_owner(inode, NULL, S_IFREG); + + return inode; } static int btrfs_init_test_fs(void) -- 2.20.1