WARNING: missing regs for base reg R10 at ip ___perf_sw_event

6 views
Skip to first unread message

syzbot

unread,
Feb 7, 2021, 12:33:18 PM2/7/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=171e2590d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=80e596b8b0902d96
dashboard link: https://syzkaller.appspot.com/bug?extid=5a3a028b17c197d66433

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

WARNING: missing regs for base reg R10 at ip ___perf_sw_event+0x28/0x480 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:7788
f2fs_msg: 6 callbacks suppressed
F2FS-fs (loop2): Magic Mismatch, valid(0xf2f52010) - read(0x8b5380f7)
F2FS-fs (loop2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (loop2): Unable to read 2th superblock
F2FS-fs (loop2): Magic Mismatch, valid(0xf2f52010) - read(0x8b5380f7)
F2FS-fs (loop2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (loop2): Unable to read 2th superblock
F2FS-fs (loop2): Magic Mismatch, valid(0xf2f52010) - read(0x8b5380f7)
F2FS-fs (loop2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (loop2): Unable to read 2th superblock
F2FS-fs (loop2): Magic Mismatch, valid(0xf2f52010) - read(0x8b5380f7)
(syz-executor.2,23237,1):ocfs2_parse_options:1484 ERROR: Unrecognized mount option "/dev/vmci" or missing value
(syz-executor.2,23237,1):ocfs2_fill_super:1217 ERROR: status = -22
hfsplus: unable to parse mount options


---
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 7, 2021, 1:32:19 PM6/7/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