Hello,
syzbot found the following issue on:
HEAD commit: 8a1d809b0545 Linux 5.15.142
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=126bc8aee80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=ee92f7141049e8f2
dashboard link:
https://syzkaller.appspot.com/bug?extid=96a7fa5abd0a78c6e89f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/8965895d90e2/disk-8a1d809b.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/f8d2c2cd9799/vmlinux-8a1d809b.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/4fa328be23e7/bzImage-8a1d809b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+96a7fa...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5721 at fs/attr.c:398 notify_change+0xcf0/0xf50
Modules linked in:
CPU: 0 PID: 5721 Comm: syz-executor.3 Not tainted 5.15.142-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:notify_change+0xcf0/0xf50 fs/attr.c:398
Code: ee e8 84 c9 f2 01 48 89 ef 89 de e8 2a 0e f3 01 45 31 f6 44 89 f0 48 83 c4 60 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 e0 2b a3 ff <0f> 0b e9 d7 f3 ff ff 44 89 f1 80 e1 07 fe c1 38 c1 0f 8c 5a f3 ff
RSP: 0018:ffffc90006127c08 EFLAGS: 00010287
RAX: ffffffff81dcf9f0 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc9000d1f3000 RSI: 00000000000067b1 RDI: 00000000000067b2
RBP: ffffc90006127d60 R08: ffffffff81dcedc0 R09: ffffed10107fde3b
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffffffff8c7ccac0 R14: ffff888083fef0f0 R15: ffff888080b95490
FS: 00007f9e31cf26c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fec09d94978 CR3: 00000000159e9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
chown_common+0x592/0x890 fs/open.c:680
do_fchownat+0x169/0x240 fs/open.c:711
__do_sys_lchown fs/open.c:736 [inline]
__se_sys_lchown fs/open.c:734 [inline]
__x64_sys_lchown+0x81/0x90 fs/open.c:734
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f9e33791ba9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9e31cf20c8 EFLAGS: 00000246 ORIG_RAX: 000000000000005e
RAX: ffffffffffffffda RBX: 00007f9e338b1050 RCX: 00007f9e33791ba9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000100
RBP: 00007f9e337dd47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f9e338b1050 R15: 00007fff0cd99a28
</TASK>
---
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