BUG: unable to handle kernel NULL pointer dereference in bdi_put

5 views
Skip to first unread message

syzbot

unread,
Dec 18, 2020, 2:14:12 AM12/18/20
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 14240d4c Add linux-next specific files for 20201210
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15a4527b500000
kernel config: https://syzkaller.appspot.com/x/.config?x=6dbe20fdaa5aaebe
dashboard link: https://syzkaller.appspot.com/bug?extid=8b0c095e42743298b166
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8b0c09...@syzkaller.appspotmail.com

BUG: kernel NULL pointer dereference, address: 0000000000000040
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 2d443067
P4D 2d443067
PUD 18868067
PMD 0

Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 19733 Comm: syz-executor.0 Not tainted 5.10.0-rc7-next-20201210-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:arch_atomic_fetch_sub arch/x86/include/asm/atomic.h:190 [inline]
RIP: 0010:atomic_fetch_sub_release include/asm-generic/atomic-instrumented.h:221 [inline]
RIP: 0010:__refcount_sub_and_test include/linux/refcount.h:272 [inline]
RIP: 0010:__refcount_dec_and_test include/linux/refcount.h:315 [inline]
RIP: 0010:refcount_dec_and_test include/linux/refcount.h:333 [inline]
RIP: 0010:kref_put include/linux/kref.h:64 [inline]
RIP: 0010:bdi_put+0x22/0xa0 mm/backing-dev.c:901
Code: 0f 1f 84 00 00 00 00 00 41 54 55 48 89 fd 53 4c 8d 65 40 bb ff ff ff ff e8 4b 23 d2 ff be 04 00 00 00 4c 89 e7 e8 6e 82 15 00 <f0> 0f c1 5d 40 bf 01 00 00 00 89 de e8 ad 2a d2 ff 83 fb 01 74 2d
RSP: 0018:ffffc900093ff860 EFLAGS: 00010202

RAX: 0000000000000001 RBX: 00000000ffffffff RCX: ffffffff81a079d2
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000040
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000044
R10: ffffffff81c80e5d R11: 0000000000000001 R12: 0000000000000040
R13: ffff888019c45920 R14: ffffffff89796aa0 R15: ffff88808e39a980
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000040 CR3: 000000001b020000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
bdev_evict_inode+0x280/0x4a0 fs/block_dev.c:809
evict+0x2ed/0x6b0 fs/inode.c:577
iput_final fs/inode.c:1651 [inline]
iput.part.0+0x41e/0x840 fs/inode.c:1677
iput+0x58/0x70 fs/inode.c:1667
dentry_unlink_inode+0x2b1/0x3d0 fs/dcache.c:374
__dentry_kill+0x3c0/0x640 fs/dcache.c:579
dentry_kill fs/dcache.c:705 [inline]
dput+0x786/0xc10 fs/dcache.c:878
do_one_tree fs/dcache.c:1625 [inline]
shrink_dcache_for_umount+0x11f/0x330 fs/dcache.c:1639
generic_shutdown_super+0x68/0x370 fs/super.c:447
kill_anon_super+0x36/0x60 fs/super.c:1055
deactivate_locked_super+0x94/0x160 fs/super.c:335
deactivate_super+0xad/0xd0 fs/super.c:366
cleanup_mnt+0x3a3/0x530 fs/namespace.c:1123
task_work_run+0xdd/0x190 kernel/task_work.c:140
exit_task_work include/linux/task_work.h:30 [inline]
do_exit+0xb89/0x2a00 kernel/exit.c:823
do_group_exit+0x125/0x310 kernel/exit.c:920
get_signal+0x3e9/0x2160 kernel/signal.c:2770
arch_do_signal_or_restart+0x2a8/0x1eb0 arch/x86/kernel/signal.c:811
handle_signal_work kernel/entry/common.c:147 [inline]
exit_to_user_mode_loop kernel/entry/common.c:171 [inline]
exit_to_user_mode_prepare+0x124/0x200 kernel/entry/common.c:201
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:302
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45e159
Code: Unable to access opcode bytes at RIP 0x45e12f.
RSP: 002b:00007fa60d624c68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffea RBX: 0000000000000005 RCX: 000000000045e159
RDX: 00000000200001c0 RSI: 0000000020000300 RDI: 0000000000000000
RBP: 000000000119c318 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000119c2d4
R13: 00007fff889a3ccf R14: 00007fa60d6259c0 R15: 000000000119c2d4
Modules linked in:
CR2: 0000000000000040
---[ end trace 3c718b6fc22fd103 ]---
RIP: 0010:arch_atomic_fetch_sub arch/x86/include/asm/atomic.h:190 [inline]
RIP: 0010:atomic_fetch_sub_release include/asm-generic/atomic-instrumented.h:221 [inline]
RIP: 0010:__refcount_sub_and_test include/linux/refcount.h:272 [inline]
RIP: 0010:__refcount_dec_and_test include/linux/refcount.h:315 [inline]
RIP: 0010:refcount_dec_and_test include/linux/refcount.h:333 [inline]
RIP: 0010:kref_put include/linux/kref.h:64 [inline]
RIP: 0010:bdi_put+0x22/0xa0 mm/backing-dev.c:901
Code: 0f 1f 84 00 00 00 00 00 41 54 55 48 89 fd 53 4c 8d 65 40 bb ff ff ff ff e8 4b 23 d2 ff be 04 00 00 00 4c 89 e7 e8 6e 82 15 00 <f0> 0f c1 5d 40 bf 01 00 00 00 89 de e8 ad 2a d2 ff 83 fb 01 74 2d
RSP: 0018:ffffc900093ff860 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 00000000ffffffff RCX: ffffffff81a079d2
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000040
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000044
R10: ffffffff81c80e5d R11: 0000000000000001 R12: 0000000000000040
R13: ffff888019c45920 R14: ffffffff89796aa0 R15: ffff88808e39a980
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000040 CR3: 000000001b020000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Feb 19, 2021, 4:51:17 AM2/19/21
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages