WARNING: missing regs for base reg R10 at ip __mutex_lock
13 views
Skip to first unread message
syzbot
Mar 21, 2020, 2:53:18 AM3/21/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 01364dad Linux 4.14.174
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=161d4f55e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=664dd71881ab2b2d
dashboard link: https://syzkaller.appspot.com/bug?extid=7574c8b5fe2b63ff71ee
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+7574c8...@syzkaller.appspotmail.com
EXT4-fs (loop3): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode table for group 0 overlaps superblock
EXT4-fs (loop3): corrupt root inode, run e2fsck
EXT4-fs (loop3): mount failed
WARNING: missing regs for base reg R10 at ip __mutex_lock+0x2d/0x1470 kernel/locking/mutex.c:892
EXT4-fs (loop3): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode table for group 0 overlaps superblock
EXT4-fs (loop3): corrupt root inode, run e2fsck
EXT4-fs (loop3): mount failed
EXT4-fs (loop3): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode table for group 0 overlaps superblock
EXT4-fs (loop3): corrupt root inode, run e2fsck
EXT4-fs (loop3): mount failed
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following crash on:
HEAD commit: 01364dad Linux 4.14.174
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=161d4f55e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=664dd71881ab2b2d
dashboard link: https://syzkaller.appspot.com/bug?extid=7574c8b5fe2b63ff71ee
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+7574c8...@syzkaller.appspotmail.com
EXT4-fs (loop3): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode table for group 0 overlaps superblock
EXT4-fs (loop3): corrupt root inode, run e2fsck
EXT4-fs (loop3): mount failed
WARNING: missing regs for base reg R10 at ip __mutex_lock+0x2d/0x1470 kernel/locking/mutex.c:892
EXT4-fs (loop3): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode table for group 0 overlaps superblock
EXT4-fs (loop3): corrupt root inode, run e2fsck
EXT4-fs (loop3): mount failed
EXT4-fs (loop3): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock
EXT4-fs (loop3): ext4_check_descriptors: Inode table for group 0 overlaps superblock
EXT4-fs (loop3): corrupt root inode, run e2fsck
EXT4-fs (loop3): mount failed
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Jul 19, 2020, 2:53:13 AM7/19/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages