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

0 views
Skip to first unread message

syzbot

unread,
Apr 9, 2024, 5:55:25 AMApr 9
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14668f4b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=4d90a36f0cab495a
dashboard link: https://syzkaller.appspot.com/bug?extid=20f3f42f0f4d77a315e8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
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/72ab73815344/disk-fe46a7dd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2d6d6b0d7071/vmlinux-fe46a7dd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/48e275e5478b/bzImage-fe46a7dd.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5604 at fs/attr.c:388 notify_change+0xc0d/0xe70 fs/attr.c:388
Modules linked in:
CPU: 1 PID: 5604 Comm: syz-executor.4 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:notify_change+0xc0d/0xe70 fs/attr.c:388
Code: 28 4c 89 e6 89 da e8 d2 60 47 02 45 31 f6 44 89 f0 48 83 c4 60 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 24 ba 86 ff 90 <0f> 0b 90 e9 bf f4 ff ff 44 89 f1 80 e1 07 fe c1 38 c1 0f 8c 41 f4
RSP: 0018:ffffc9000a00fbe8 EFLAGS: 00010287
RAX: ffffffff820e3a2c RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc9000a441000 RSI: 0000000000003655 RDI: 0000000000003656
RBP: ffffffff8e26eda0 R08: ffffffff820e2ee6 R09: 1ffff1100eefc152
R10: dffffc0000000000 R11: ffffed100eefc153 R12: ffff88807c546eb0
R13: ffffc9000a00fd40 R14: ffff8880777e09b0 R15: dffffc0000000000
FS: 00007fd4e626f6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30a23000 CR3: 000000002bfec000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
chown_common+0x501/0x850 fs/open.c:790
do_fchownat+0x16d/0x250 fs/open.c:821
__do_sys_lchown fs/open.c:846 [inline]
__se_sys_lchown fs/open.c:844 [inline]
__x64_sys_lchown+0x85/0xa0 fs/open.c:844
do_syscall_64+0xfb/0x240
entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7fd4e547de69
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:00007fd4e626f0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000005e
RAX: ffffffffffffffda RBX: 00007fd4e55abf80 RCX: 00007fd4e547de69
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000040
RBP: 00007fd4e54ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fd4e55abf80 R15: 00007ffe95132d68
</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