Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp9178801pxu; Mon, 28 Dec 2020 08:32:16 -0800 (PST) X-Google-Smtp-Source: ABdhPJwlu22lTNF8sBVce88WXvGc7CXusD7j/lJWghjd+r/Lg2lcv2vn/W07tyu5dnK6BB/cPX8A X-Received: by 2002:a05:6402:c0b:: with SMTP id co11mr42099245edb.180.1609173136337; Mon, 28 Dec 2020 08:32:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609173136; cv=none; d=google.com; s=arc-20160816; b=b2mgFHf94BGxTPhzfw1ylq+6RxzfLjoVB0fVFXOaQz/37XT0AMEjNEs1GpeO/M1jcz fS4GHv2SdSFIP42vRqmF2UUmuvEymGNzhvQ5v/rsrbovsebHPzdtyJsDsMHeY49/eQnA uaLUUameTIClJVEzXO+pqb4pxOqgXzH10phgOA2QfNaYN0is3PRRV0KtEqCu5ZRvJZPZ qmg0+YRFthx0VWciKNbs2JoX2QBqYX8AXYux9wr6yPaKsfA2Z4U7imaqXQmezjPDX69w BNnzjqNRW30JaRpiNutGPrya1qbsJYOQiszomMI4VALxBRQHbCudZLNS0/baYD7Z/vXc WbRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=iTpEHxefwo/QZr2/j4OeqwdAjLK03uZbsKJbGTcpqnI=; b=dwFNiKPSjfCQXfGcuuT6mAWjS8bPg6TCMXgeewLgzcs4X14f9zTKFK5IxaFT5pKxyk nhzn1Y4HcN88lhZrFt8PMIm8PyHZZxCWoL2fAZkP5DQ9fs5TRtDqJka0Q1VTXTCFQ+ef GXUPBiSZqKKx3kSwSJTqwIFIuZAyC73h8QQGnbC8tITkNMQtyQm1H6ZiNiOlhKGEPBYW Z+64bgf94osKrXEU6Y5+VKbYPeU/r+isaK2iEmu93uSUYO8mdA19MmlWmgonkn6Bs4Nn /VMUI42G5JNcBlwjO10F6hUeXv316YR3BQg2KT9T0b0+87HL2/IaVbcY/tTCpN51L9KM 0lJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=koftqpHc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o4si18219326ejr.495.2020.12.28.08.31.53; Mon, 28 Dec 2020 08:32:16 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=koftqpHc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2633654AbgL1Q3x (ORCPT + 99 others); Mon, 28 Dec 2020 11:29:53 -0500 Received: from mail.kernel.org ([198.145.29.99]:34840 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730683AbgL1NHH (ORCPT ); Mon, 28 Dec 2020 08:07:07 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 7DA342245C; Mon, 28 Dec 2020 13:06:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1609160786; bh=HVbqvAAOwKCjeUuSvkGAPBsS4i41WktIU71zxCGbU5s=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=koftqpHcv46NHwonWhqnm+S72Xtuaok51AYjdVrjn3S7cCG5AWm05KsIqaiaoYxjx d8E6TbO/wksNJYoDmKGRoXppXS6fZWNlJRt+bjdc0fUSY1OuHRdc2vRPJezkOn2O3h 7OsXue/WwW/fuSCJj2RNtHuZfTdANICodxuCgmwU= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Filipe Manana , Qu Wenruo , David Sterba , Sudip Mukherjee Subject: [PATCH 4.9 153/175] Btrfs: fix selftests failure due to uninitialized i_mode in test inodes Date: Mon, 28 Dec 2020 13:50:06 +0100 Message-Id: <20201228124900.670519237@linuxfoundation.org> X-Mailer: git-send-email 2.29.2 In-Reply-To: <20201228124853.216621466@linuxfoundation.org> References: <20201228124853.216621466@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Filipe Manana commit 9f7fec0ba89108b9385f1b9fb167861224912a4a upstream 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: Sudip Mukherjee Signed-off-by: Greg Kroah-Hartman --- fs/btrfs/tests/btrfs-tests.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) --- 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)