From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 215922] New: KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
Date: Sat, 30 Apr 2022 08:08:38 +0000 [thread overview]
Message-ID: <bug-215922-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215922
Bug ID: 215922
Summary: KASAN: null-ptr-deref in range
[0x0000000000000000-0x0000000000000007]
Product: File System
Version: 2.5
Kernel Version: 5.17
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: yanming@tju.edu.cn
Regression: No
Created attachment 300859
--> https://bugzilla.kernel.org/attachment.cgi?id=300859&action=edit
case.c, which contains the related file operations.
I've encountered an issue when using XFS file system in kernel 5.17.
When I tried to run some file operations, a segmentation fault occurred, and I
failed to umount the XFS image.
The related file operations are listed in case.c, and I have uploaded the XFS
image on the google net disk
(https://drive.google.com/file/d/1RJMr1AKtLtev8dinHBawWa7tTvHEytr3/view?usp=sharing).
The kernel should be configured with CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y.
You can reproduce this issue by running the following commands:
gcc -o case case.c
losetup /dev/loop0 case.img
mount -o
"allocsize=4096,attr2,discard,nogrpid,filestreams,noikeep,noalign,wsync"
/dev/loop0 /mnt/test/
./case
The kernel outputted the following messages:
1,1310,83736925,-;KASAN: null-ptr-deref in range
[0x0000000000000000-0x0000000000000007]
4,1311,83736935,-;CPU: 6 PID: 1099 Comm: case Not tainted 5.17.0 #7
4,1312,83736943,-;Hardware name: Dell Inc. OptiPlex 9020/03CPWF, BIOS A14
09/14/2015
4,1313,83736951,-;RIP: 0010:xfs_dir_isempty+0xfe/0x240
4,1314,83736962,-;Code: 48 8d 7b 60 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 38
01 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 5b 60 48 89 da 48 c1 ea 03 <0f> b6
04 02 48 89 da 83 e2 07 38 d0 7f 08 84 c0 0f 85 17 01 00 00
4,1315,83736977,-;RSP: 0018:ffff88810300fca0 EFLAGS: 00010246
4,1316,83736986,-;RAX: dffffc0000000000 RBX: 0000000000000000 RCX:
1ffff11022dc4450
4,1317,83736995,-;RDX: 0000000000000000 RSI: 0000000000000008 RDI:
ffff888151cb84a0
4,1318,83737003,-;RBP: 00000000000000eb R08: 0000000000000000 R09:
ffffed102a394829
4,1319,83737011,-;R10: ffff888151ca4147 R11: ffffed102a394828 R12:
ffff888116e22000
4,1320,83737020,-;R13: 1ffff11020601f9d R14: ffff88810300fda8 R15:
0000000000004000
4,1321,83737028,-;FS: 00007f1c7b968540(0000) GS:ffff8881cff80000(0000)
knlGS:0000000000000000
4,1322,83737039,-;CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
4,1323,83737046,-;CR2: 00007f1c7b88d750 CR3: 0000000113980001 CR4:
00000000001706e0
4,1324,83737055,-;Call Trace:
4,1325,83737060,-; <TASK>
4,1326,83737065,-; xfs_remove+0x5f0/0x890
4,1327,83737074,-; ? try_to_take_rt_mutex+0x3bd/0xb70
4,1328,83737083,-; ? xfs_iunpin_wait+0x3c0/0x3c0
4,1329,83737091,-; ? may_link+0x2af/0x380
4,1330,83737099,-; ? selinux_inode_rename+0x770/0x770
4,1331,83737108,-; xfs_vn_unlink+0xf3/0x200
4,1332,83737116,-; ? xfs_vn_rename+0x400/0x400
4,1333,83737125,-; ? security_inode_rmdir+0x95/0xe0
4,1334,83737133,-; vfs_rmdir+0x219/0x560
4,1335,83737142,-; ? __lookup_hash+0x1b/0x150
4,1336,83737151,-; do_rmdir+0x246/0x300
4,1337,83737159,-; ? __x64_sys_mkdir+0x70/0x70
4,1338,83737166,-; ? kasan_unpoison+0x23/0x50
4,1339,83737175,-; ? kmem_cache_alloc+0x10f/0x220
4,1340,83737184,-; ? getname_flags+0xf8/0x4e0
4,1341,83737193,-; __x64_sys_rmdir+0x39/0x50
4,1342,83737201,-; do_syscall_64+0x3b/0x90
4,1343,83737209,-; entry_SYSCALL_64_after_hwframe+0x44/0xae
4,1344,83737219,-;RIP: 0033:0x7f1c7b88d76d
4,1345,83737226,-;Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48
89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d
01 f0 ff ff 73 01 c3 48 8b 0d f3 36 0d 00 f7 d8 64 89 01 48
4,1346,83737241,-;RSP: 002b:00007ffe5f49b288 EFLAGS: 00000286 ORIG_RAX:
0000000000000054
4,1347,83737252,-;RAX: ffffffffffffffda RBX: 000055a1f772e600 RCX:
00007f1c7b88d76d
4,1348,83737260,-;RDX: ffffffffffffff80 RSI: ffffffffffffff80 RDI:
00007ffe5f49b2b6
4,1349,83737268,-;RBP: 00007ffe5f89b400 R08: 00007ffe5f89b4f8 R09:
00007ffe5f89b4f8
4,1350,83737276,-;R10: 00007ffe5f89b4f8 R11: 0000000000000286 R12:
000055a1f772e0a0
4,1351,83737284,-;R13: 00007ffe5f89b4f0 R14: 0000000000000000 R15:
0000000000000000
4,1352,83737294,-; </TASK>
4,1353,83737299,-;Modules linked in: x86_pkg_temp_thermal efivarfs
4,1354,83737331,-;---[ end trace 0000000000000000 ]---
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-04-30 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 8:08 bugzilla-daemon [this message]
2022-05-05 6:23 ` [Bug 215922] New: KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] Darrick J. Wong
2022-05-05 6:23 ` [Bug 215922] " bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-215922-201763@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.