Btrfs: fix selftests failure due to uninitialized i_mode in test inodes
PATCH 1/1 Btrfs: fix selftests failure due to uninitialized i_mode in test inodes
From: Filipe Manana <[email protected]>
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().
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204397
--- fs/btrfs/tests/btrfs-tests.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
fs/btrfs/tests/btrfs-tests.c +7 -1
@@ -52,7 +52,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 )
Signature · 1 line
2.11.0
Quoted 46 lines · On 2019/9/18 下午8:08, [email protected] wrote:
From: Filipe Manana <[email protected]>
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. Howeverbtrfs_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 notS_IFREG). This causes the self tests to fail sometimes, specially when KASAN,slub_debugand 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 0This happens because the test inodes are created without ever initializing the
i_modefield of the inode, and neither VFS'snew_inode()nor the btrfs callbackbtrfs_alloc_inode()initialize thei_mode. Initialization of thei_modeis done through the various callbacks used by the VFS to create new inodes (regular files, directories, symlinks, tmpfiles, etc), which all callbtrfs_new_inode()which in turn callsinode_init_owner(), which sets the inode'si_mode. Since the tests only usesnew_inode()to create the test inodes, thei_modewas never initialized.This always happens on a VM I used with kasan,
slub_debugand many other debug facilities enabled. It also happened to someone who reported this on bugzilla (on a 5.3-rc).
Quoted 5 lines
Fix this by setting
i_modetoS_IFREGatbtrfs_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 <[email protected]>
However I'm interested why it doesn't get triggered reliably. As I have selftest compiled in everytime.
Is there anything racy caused the bug?
Thanks,
Qu
Quoted 24 lines
--- fs/btrfs/tests/btrfs-tests.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)fs/btrfs/tests/btrfs-tests.c +7
-1@@ -52,7 +52,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 )
Quoted 56 lines · Qu Wenruo
Quoted 46 lines · On 2019/9/18 下午8:08, [email protected] wrote:
From: Filipe Manana <[email protected]>
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. Howeverbtrfs_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 notS_IFREG). This causes the self tests to fail sometimes, specially when KASAN,slub_debugand 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 0This happens because the test inodes are created without ever initializing the
i_modefield of the inode, and neither VFS'snew_inode()nor the btrfs callbackbtrfs_alloc_inode()initialize thei_mode. Initialization of thei_modeis done through the various callbacks used by the VFS to create new inodes (regular files, directories, symlinks, tmpfiles, etc), which all callbtrfs_new_inode()which in turn callsinode_init_owner(), which sets the inode'si_mode. Since the tests only usesnew_inode()to create the test inodes, thei_modewas never initialized.This always happens on a VM I used with kasan,
slub_debugand many other debug facilities enabled. It also happened to someone who reported this on bugzilla (on a 5.3-rc).Quoted 5 lines
Fix this by setting
i_modetoS_IFREGatbtrfs_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 <[email protected]>
Quoted 6 lines
Reviewed-by Qu Wenruo <[email protected]>However I'm interested why it doesn't get triggered reliably. As I have selftest compiled in everytime.
Is there anything racy caused the bug?
Nop (otherwise I would have noted that in the changelog).
It's just garbage due to uninitialized memory.
In this case, btrfs is a module and only used for testing, since a btrfs inode was never allocated before attempting to load the module and run the selftests, we get the garbage. If we had a non-testing inode allocated and freed before running the tests, the i_mode of the test inode would match the one from previously freed inode.
Quoted 29 lines
Thanks,
QuQuoted 24 lines
--- fs/btrfs/tests/btrfs-tests.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)fs/btrfs/tests/btrfs-tests.c +7
-1@@ -52,7 +52,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 )
Quoted 62 lines · Filipe Manana
Quoted 61 lines · Qu Wenruo
Quoted 46 lines · On 2019/9/18 下午8:08, [email protected] wrote:
From: Filipe Manana <[email protected]>
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. Howeverbtrfs_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 notS_IFREG). This causes the self tests to fail sometimes, specially when KASAN,slub_debugand 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 0This happens because the test inodes are created without ever initializing the
i_modefield of the inode, and neither VFS'snew_inode()nor the btrfs callbackbtrfs_alloc_inode()initialize thei_mode. Initialization of thei_modeis done through the various callbacks used by the VFS to create new inodes (regular files, directories, symlinks, tmpfiles, etc), which all callbtrfs_new_inode()which in turn callsinode_init_owner(), which sets the inode'si_mode. Since the tests only usesnew_inode()to create the test inodes, thei_modewas never initialized.This always happens on a VM I used with kasan,
slub_debugand many other debug facilities enabled. It also happened to someone who reported this on bugzilla (on a 5.3-rc).Quoted 5 lines
Fix this by setting
i_modetoS_IFREGatbtrfs_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 <[email protected]>Reviewed-by Qu Wenruo <[email protected]>However I'm interested why it doesn't get triggered reliably. As I have selftest compiled in everytime.
Quoted 8 lines
Quoted 1 line
Is there anything racy caused the bug?
Nop (otherwise I would have noted that in the changelog).
It's just garbage due to uninitialized memory.
In this case, btrfs is a module and only used for testing, since a btrfs inode was never allocated before attempting to load the module and run the selftests, we get the garbage.
That makes sense.
Thanks for the fix!
Qu
Quoted 33 lines
If we had a non-testing
inode allocated and freed before running the tests, thei_modeof the test inode would match the one from previously freed inode.Quoted 29 lines
Thanks,
QuQuoted 24 lines
--- fs/btrfs/tests/btrfs-tests.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)fs/btrfs/tests/btrfs-tests.c +7
-1@@ -52,7 +52,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 )
Quoted 46 lines · On Wed, Sep 18, 2019 at 01:08:52PM +0100, [email protected] wrote:
From: Filipe Manana <[email protected]>
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. Howeverbtrfs_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 notS_IFREG). This causes the self tests to fail sometimes, specially when KASAN,slub_debugand 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 0This happens because the test inodes are created without ever initializing the
i_modefield of the inode, and neither VFS'snew_inode()nor the btrfs callbackbtrfs_alloc_inode()initialize thei_mode. Initialization of thei_modeis done through the various callbacks used by the VFS to create new inodes (regular files, directories, symlinks, tmpfiles, etc), which all callbtrfs_new_inode()which in turn callsinode_init_owner(), which sets the inode'si_mode. Since the tests only usesnew_inode()to create the test inodes, thei_modewas never initialized.This always happens on a VM I used with kasan,
slub_debugand many other debug facilities enabled. It also happened to someone who reported this on bugzilla (on a 5.3-rc).
Quoted 5 lines
Fix this by setting
i_modetoS_IFREGatbtrfs_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 <[email protected]>
Added to misc-next, thanks.