Hello,
syzbot found the following issue on:
HEAD commit: 2965db2e Linux 4.19.188
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16d7325dd00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=66e717310a9b0f81
dashboard link:
https://syzkaller.appspot.com/bug?extid=2d948a60d5065c36f880
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+2d948a...@syzkaller.appspotmail.com
lo: Cannot use loopback or non-ethernet device as HSR slave.
erofs: root inode @ nid 36
erofs: mounted on /dev/loop1 with opts: .
device batadv0 left promiscuous mode
------------[ cut here ]------------
kernel BUG at drivers/staging/erofs/xattr.c:186!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 11281 Comm: syz-executor.1 Not tainted 4.19.188-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:inline_xattr_iter_begin+0x3c4/0x4a0 drivers/staging/erofs/xattr.c:186
Code: 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 56 96 28 fb 44 89 ee 89 ef 41 bc c3 ff ff ff e8 36 97 28 fb 44 39 ed 73 cf e8 3c 96 28 fb <0f> 0b e8 35 96 28 fb 41 89 ec eb be e8 db 56 5e fb e9 b9 fc ff ff
RSP: 0018:ffff888043d8fc88 EFLAGS: 00010216
RAX: 0000000000040000 RBX: ffff88804313e500 RCX: ffffc9000803f000
RDX: 0000000000000591 RSI: ffffffff8639c784 RDI: 0000000000000004
RBP: 0000000000000048 R08: 0000000000000001 R09: 0000000000000048
R10: 0000000000000004 R11: 0000000000000000 R12: 00000000ffffffc3
R13: 0000000000000280 R14: ffff88804313e4ea R15: ffff88809c94a000
FS: 00007f900024d700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056463ce8c8c8 CR3: 0000000098d8d000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
inline_listxattr drivers/staging/erofs/xattr.c:584 [inline]
erofs_listxattr+0x147/0xf10 drivers/staging/erofs/xattr.c:653
vfs_listxattr+0x105/0x190 fs/xattr.c:392
listxattr+0x70/0x140 fs/xattr.c:687
path_listxattr+0xae/0x140 fs/xattr.c:711
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4665f9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f900024d188 EFLAGS: 00000246 ORIG_RAX: 00000000000000c2
RAX: ffffffffffffffda RBX: 000000000056c008 RCX: 00000000004665f9
RDX: 0000000000001000 RSI: 0000000020000280 RDI: 00000000200000c0
RBP: 00000000004bfbb9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056c008
R13: 00007fffbe5f2c6f R14: 00007f900024d300 R15: 0000000000022000
Modules linked in:
---[ end trace 0eb13a98977b4716 ]---
RIP: 0010:inline_xattr_iter_begin+0x3c4/0x4a0 drivers/staging/erofs/xattr.c:186
Code: 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 56 96 28 fb 44 89 ee 89 ef 41 bc c3 ff ff ff e8 36 97 28 fb 44 39 ed 73 cf e8 3c 96 28 fb <0f> 0b e8 35 96 28 fb 41 89 ec eb be e8 db 56 5e fb e9 b9 fc ff ff
RSP: 0018:ffff888043d8fc88 EFLAGS: 00010216
RAX: 0000000000040000 RBX: ffff88804313e500 RCX: ffffc9000803f000
RDX: 0000000000000591 RSI: ffffffff8639c784 RDI: 0000000000000004
RBP: 0000000000000048 R08: 0000000000000001 R09: 0000000000000048
R10: 0000000000000004 R11: 0000000000000000 R12: 00000000ffffffc3
R13: 0000000000000280 R14: ffff88804313e4ea R15: ffff88809c94a000
FS: 00007f900024d700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f427b93d8b0 CR3: 0000000098d8d000 CR4: 00000000001406e0
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.