[v6.1] WARNING in notify_change (2)

2 views
Skip to first unread message

syzbot

unread,
Jun 2, 2025, 9:11:29 PM6/2/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: da3c5173c55f Linux 6.1.140
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11cb5c82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=46e5b914cae7bc26
dashboard link: https://syzkaller.appspot.com/bug?extid=423874fcec7c3f909b33
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f64777e3df5f/disk-da3c5173.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/86760acf06d3/vmlinux-da3c5173.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4b53296c1a0a/bzImage-da3c5173.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 7753 at fs/attr.c:390 notify_change+0xce9/0xf40 fs/attr.c:390
Modules linked in:
CPU: 0 PID: 7753 Comm: syz.1.1410 Not tainted 6.1.140-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:notify_change+0xce9/0xf40 fs/attr.c:390
Code: 89 e6 e8 9a 2a e9 01 4c 89 e7 44 89 ee e8 6f 69 e9 01 31 db 89 d8 48 83 c4 58 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 47 2d 99 ff <0f> 0b e9 dd f3 ff ff 89 e9 80 e1 07 fe c1 38 c1 0f 8c 64 f3 ff ff
RSP: 0018:ffffc900048dfc10 EFLAGS: 00010283
RAX: ffffffff81e7a9c9 RBX: 0000000000000000 RCX: 0000000000080000
RDX: ffffc9000e872000 RSI: 000000000000595c RDI: 000000000000595d
RBP: ffff88805533eb80 R08: dffffc0000000000 R09: ffffed100aa67d8d
R10: ffffed100aa67d8d R11: 1ffff1100aa67d8c R12: ffffc900048dfd40
R13: ffff888070bbea48 R14: 0000000000000046 R15: dffffc0000000000
FS: 00007f11a63146c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f11a6313f98 CR3: 0000000029741000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
chown_common+0x486/0x620 fs/open.c:736
do_fchownat+0x164/0x270 fs/open.c:767
__do_sys_fchownat fs/open.c:782 [inline]
__se_sys_fchownat fs/open.c:779 [inline]
__x64_sys_fchownat+0xb1/0xc0 fs/open.c:779
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f11a558e969
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f11a6314038 EFLAGS: 00000246 ORIG_RAX: 0000000000000104
RAX: ffffffffffffffda RBX: 00007f11a57b6080 RCX: 00007f11a558e969
RDX: 0000000000000000 RSI: 0000200000000000 RDI: ffffffffffffff9c
RBP: 00007f11a5610ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f11a57b6080 R15: 00007ffe096b5a28
</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

syzbot

unread,
Sep 10, 2025, 9:11:22 PM9/10/25
to syzkaller...@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