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

7 views
Skip to first unread message

syzbot

unread,
Oct 25, 2023, 4:14:58 PM10/25/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9c5d00cb7b6b Merge tag 'perf-tools-fixes-for-v6.6-2-2023-1..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=145c4e05680000
kernel config: https://syzkaller.appspot.com/x/.config?x=530f7d8ed0a57417
dashboard link: https://syzkaller.appspot.com/bug?extid=304b0e676c8ae989bf66
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org 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/9136b1192819/disk-9c5d00cb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f34715d57d99/vmlinux-9c5d00cb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6c9f17aaf192/bzImage-9c5d00cb.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5336 at fs/attr.c:390 notify_change+0xb3b/0x11c0 fs/attr.c:390
Modules linked in:
CPU: 1 PID: 5336 Comm: syz-executor.5 Not tainted 6.6.0-rc6-syzkaller-00285-g9c5d00cb7b6b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
RIP: 0010:notify_change+0xb3b/0x11c0 fs/attr.c:390
Code: bf ff ff ff ff 89 45 b0 e8 42 cc 92 ff 8b 45 b0 83 f8 ff 0f 85 c5 fa ff ff c7 45 bc b5 ff ff ff e9 27 fc ff ff e8 b5 d0 92 ff <0f> 0b e9 ad f5 ff ff e8 a9 d0 92 ff 45 89 e7 4c 89 f2 48 b8 00 00
RSP: 0018:ffffc9000537fca0 EFLAGS: 00010287
RAX: 0000000000009547 RBX: ffffc9000537fdb0 RCX: ffffc9000ab9e000
RDX: 0000000000040000 RSI: ffffffff81f4f93b RDI: 0000000000000007
RBP: ffffc9000537fd08 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: ffffc9000537fea8 R14: ffff88803a539870 R15: 0000000000000046
FS: 00007f9466d006c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3003e000 CR3: 000000006881c000 CR4: 0000000000350ee0
Call Trace:
<TASK>
chown_common+0x596/0x660 fs/open.c:783
do_fchownat+0x140/0x1f0 fs/open.c:814
__do_sys_chown fs/open.c:834 [inline]
__se_sys_chown fs/open.c:832 [inline]
__x64_sys_chown+0x7b/0xc0 fs/open.c:832
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f946607cae9
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:00007f9466d000c8 EFLAGS: 00000246 ORIG_RAX: 000000000000005c
RAX: ffffffffffffffda RBX: 00007f946619c050 RCX: 00007f946607cae9
RDX: 000000000000ee00 RSI: 0000000000000000 RDI: 00000000200001c0
RBP: 00007f94660c847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f946619c050 R15: 00007ffe9183b328
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jan 19, 2024, 3:10:18 PMJan 19
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages