INFO: trying to register non-static key in shmem_add_to_page_cache

12 views
Skip to first unread message

syzbot

unread,
Feb 5, 2021, 1:41:18 AM2/5/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2c8a3fce Linux 4.14.218
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=173b8c5f500000
kernel config: https://syzkaller.appspot.com/x/.config?x=80e596b8b0902d96
dashboard link: https://syzkaller.appspot.com/bug?extid=a8111eb5f04d22254005

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+a8111e...@syzkaller.appspotmail.com

INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 0 PID: 7147 Comm: systemd-udevd Not tainted 4.14.218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
register_lock_class+0x32b/0x1320 kernel/locking/lockdep.c:768
__lock_acquire+0x167/0x3f20 kernel/locking/lockdep.c:3378
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__raw_spin_lock_irq include/linux/spinlock_api_smp.h:128 [inline]
_raw_spin_lock_irq+0x5b/0x80 kernel/locking/spinlock.c:168
spin_lock_irq include/linux/spinlock.h:342 [inline]
shmem_add_to_page_cache+0x1e7/0x730 mm/shmem.c:597
shmem_getpage_gfp+0x11f0/0x28f0 mm/shmem.c:1816
shmem_getpage mm/shmem.c:131 [inline]
shmem_write_begin+0xeb/0x190 mm/shmem.c:2416
generic_perform_write+0x1c9/0x420 mm/filemap.c:3055
__generic_file_write_iter+0x227/0x590 mm/filemap.c:3180
generic_file_write_iter+0x36f/0x650 mm/filemap.c:3208
call_write_iter include/linux/fs.h:1778 [inline]
new_sync_write fs/read_write.c:469 [inline]
__vfs_write+0x44c/0x630 fs/read_write.c:482
vfs_write+0x17f/0x4d0 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f674e0fe970
RSP: 002b:00007ffd47a15138 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000000002d RCX: 00007f674e0fe970
RDX: 000000000000002d RSI: 000055b39f87b120 RDI: 000000000000000f
RBP: 000055b39f87b120 R08: 000055b39f889470 R09: 00007f674f28b8c0
R10: 0000000000000073 R11: 0000000000000246 R12: 000000000000002d
R13: 0000000000000001 R14: 000055b39f889390 R15: 000000000000002d
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 7170 Comm: systemd-udevd Not tainted 4.14.218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880387e8240 task.stack: ffff8882284f8000
RIP: 0010:__list_del_entry_valid+0x81/0xf0 lib/list_debug.c:51
RSP: 0018:ffff8882284ffc10 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff88800011ad10 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88800011ad18
RBP: ffff88800011ad10 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880387e8240 R12: 0000000000000000
R13: 0000000000000000 R14: ffff88800011abf8 R15: 0000000000000000
FS: 00007f674f28b8c0(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd47b1fc10 CR3: 0000000228de7000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_del_entry include/linux/list.h:117 [inline]
list_del_init include/linux/list.h:159 [inline]
list_lru_del+0xfe/0x4c0 mm/list_lru.c:134
inode_lru_list_del fs/inode.c:429 [inline]
iput_final fs/inode.c:1521 [inline]
iput+0x432/0x7e0 fs/inode.c:1551
dentry_unlink_inode+0x25c/0x310 fs/dcache.c:387
__dentry_kill+0x320/0x550 fs/dcache.c:591
dentry_kill fs/dcache.c:632 [inline]
dput.part.0+0x4b5/0x710 fs/dcache.c:847
dput+0x1b/0x30 fs/dcache.c:811
SYSC_renameat2 fs/namei.c:4648 [inline]
SyS_renameat2+0x96a/0xad0 fs/namei.c:4533
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f674e087d47
RSP: 002b:00007ffd47a15228 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 000055b39f88d670 RCX: 00007f674e087d47
RDX: 0000000000000000 RSI: 00007ffd47a15230 RDI: 000055b39f88e0c0
RBP: 00007ffd47a152f0 R08: 000055b39f88c6e0 R09: 000055b39f88c600
R10: 00007f674f28b8c0 R11: 0000000000000246 R12: 00007ffd47a15230
R13: 0000000000000001 R14: 000055b39dd6e6cb R15: 0000000000000000
Code: c5 0f 84 db 35 ef 03 48 b8 00 02 00 00 00 00 ad de 49 39 c4 0f 84 dc 35 ef 03 48 b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 <80> 3c 02 00 75 51 49 8b 14 24 48 39 ea 0f 85 93 35 ef 03 49 8d
RIP: __list_del_entry_valid+0x81/0xf0 lib/list_debug.c:51 RSP: ffff8882284ffc10
---[ end trace 479dd407a18d7801 ]---


---
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,
Jun 5, 2021, 2:41:15 AM6/5/21
to syzkaller...@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