[moderation] [fs?] WARNING in notify_change (10)

0 views
Skip to first unread message

syzbot

unread,
12:30 AM (16 hours ago) 12:30 AM
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: eb3f4b7426cf Merge tag 'nfsd-7.1-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10f14056580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd38685893011045
dashboard link: https://syzkaller.appspot.com/bug?extid=585661cb628f97fca0c3
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/82ff9dc3956e/disk-eb3f4b74.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/be01a7a564dd/vmlinux-eb3f4b74.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5d5168563228/bzImage-eb3f4b74.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+585661...@syzkaller.appspotmail.com

------------[ cut here ]------------
!inode_is_locked(inode)
WARNING: fs/attr.c:436 at notify_change+0xc7e/0xf60 fs/attr.c:436, CPU#1: syz.6.838/16856
Modules linked in:
CPU: 1 UID: 0 PID: 16856 Comm: syz.6.838 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:notify_change+0xc7e/0xf60 fs/attr.c:436
Code: 89 ff 4c 89 ee 89 ea e8 80 f3 17 02 31 db 89 d8 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 13 f5 82 ff 90 <0f> 0b 90 e9 57 f4 ff ff 89 d9 80 e1 07 fe c1 38 c1 0f 8c dc f3 ff
RSP: 0018:ffffc90004affbf8 EFLAGS: 00010287
RAX: ffffffff8241782d RBX: 0000000080000000 RCX: 0000000000080000
RDX: ffffc90013f9a000 RSI: 0000000000000810 RDI: 0000000000000811
RBP: 0000000000000046 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed100cc61bce R12: ffff88806630de68
R13: ffffc90004affd20 R14: ffff888040490528 R15: dffffc0000000000
FS: 00007f2baa8bd6c0(0000) GS:ffff888126486000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9cc7596cc4 CR3: 0000000097eb2000 CR4: 00000000003526f0
Call Trace:
<TASK>
chown_common+0x466/0x6c0 fs/open.c:776
do_fchownat+0x14c/0x250 fs/open.c:804
__do_sys_chown fs/open.c:824 [inline]
__se_sys_chown fs/open.c:822 [inline]
__x64_sys_chown+0x82/0xa0 fs/open.c:822
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2bac68ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2baa8bd028 EFLAGS: 00000246 ORIG_RAX: 000000000000005c
RAX: ffffffffffffffda RBX: 00007f2bac906090 RCX: 00007f2bac68ce59
RDX: 0000000000000000 RSI: 0000000000008000 RDI: 00002000000000c0
RBP: 00007f2bac722d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2bac906128 R14: 00007f2bac906090 R15: 00007ffd64378748
</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
Reply all
Reply to author
Forward
0 new messages