Hello,
syzbot found the following issue on:
HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=14215944580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=393f8074c5fb7ad6
dashboard link:
https://syzkaller.appspot.com/bug?extid=2778e0eefed09b215b38
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/3986cbf4f35a/disk-e4d90d63.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/d2963d16cebb/vmlinux-e4d90d63.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/a877a1a23701/Image-e4d90d63.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+2778e0...@syzkaller.appspotmail.com
REISERFS (device loop4): Using tea hash to sort names
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5939 at fs/inode.c:332 drop_nlink+0xe4/0x138 fs/inode.c:332
Modules linked in:
CPU: 1 PID: 5939 Comm: syz.4.357 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : drop_nlink+0xe4/0x138 fs/inode.c:332
lr : drop_nlink+0xe4/0x138 fs/inode.c:332
sp : ffff800021557540
x29: ffff800021557540 x28: ffff7000042aaeb8 x27: dfff800000000000
x26: ffff0000e1250f18 x25: 00000000ffffffff x24: 1fffe0001c24a1df
x23: 1fffe0001c24a1e3 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000e1250f18 x19: ffff0000e1250ed0 x18: ffff8000215569a0
x17: ffff800018b6a000 x16: ffff800008300db8 x15: ffff800008ad08c4
x14: ffff800008acd634 x13: ffff800008ad08c4 x12: 0000000000080000
x11: 000000000007ffff x10: ffff800024faa000 x9 : ffff800008aab0a4
x8 : 0000000000080000 x7 : ffff80000805c2c4 x6 : ffff80000805c4d4
x5 : ffff0000d138adc0 x4 : ffff800021556e68 x3 : 0000000000000000
x2 : 0000000000000006 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
drop_nlink+0xe4/0x138 fs/inode.c:332
reiserfs_mkdir+0x5e0/0x77c fs/reiserfs/namei.c:850
xattr_mkdir fs/reiserfs/xattr.c:76 [inline]
create_privroot fs/reiserfs/xattr.c:882 [inline]
reiserfs_xattr_init+0x2b0/0x6bc fs/reiserfs/xattr.c:1005
reiserfs_fill_super+0x1bfc/0x2028 fs/reiserfs/super.c:2175
mount_bdev+0x274/0x370 fs/super.c:1443
get_super_block+0x44/0x58 fs/reiserfs/super.c:2601
legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
vfs_get_tree+0x90/0x274 fs/super.c:1573
do_new_mount+0x278/0x8fc fs/namespace.c:3056
path_mount+0x590/0xe5c fs/namespace.c:3386
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount fs/namespace.c:3584 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3584
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 55208
hardirqs last enabled at (55207): [<ffff800008390e2c>] call_rcu+0x614/0xa40 kernel/rcu/tree.c:2880
hardirqs last disabled at (55208): [<ffff800012320d2c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (54538): [<ffff8000081c1c58>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (54538): [<ffff8000081c1c58>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:599
softirqs last disabled at (54525): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:605
---[ end trace 0000000000000000 ]---
REISERFS warning (device loop4): jdm-20006 create_privroot: xattrs/ACLs enabled and couldn't find/create .reiserfs_priv. Failing mount.
loop4: detected capacity change from 0 to 32768
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup