[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6745b332.050a0220.1286eb.0016.GAE@google.com>
Date: Tue, 26 Nov 2024 03:38:26 -0800
From: syzbot <syzbot+3ff7365dc04a6bcafa66@...kaller.appspotmail.com>
To: jack@...e.com, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: [syzbot] [udf?] WARNING in udf_rename (2)
Hello,
syzbot found the following issue on:
HEAD commit: 06afb0f36106 Merge tag 'trace-v6.13' of git://git.kernel.o..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=149e7930580000
kernel config: https://syzkaller.appspot.com/x/.config?x=402159daa216c89d
dashboard link: https://syzkaller.appspot.com/bug?extid=3ff7365dc04a6bcafa66
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13f8975f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=129e7930580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/77e67e959031/disk-06afb0f3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ef29cbe930b4/vmlinux-06afb0f3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/430d1fe2c7b0/bzImage-06afb0f3.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0f103b2b0acc/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3ff7365dc04a6bcafa66@...kaller.appspotmail.com
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000)
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5834 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407
Modules linked in:
CPU: 1 UID: 0 PID: 5834 Comm: syz-executor342 Not tainted 6.12.0-syzkaller-07834-g06afb0f36106 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:drop_nlink+0xc4/0x110 fs/inode.c:407
Code: bb 70 07 00 00 be 08 00 00 00 e8 27 d8 e5 ff f0 48 ff 83 70 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 cc cc cc cc e8 9d 40 7e ff 90 <0f> 0b 90 eb 83 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 5c ff ff ff
RSP: 0018:ffffc90003ab7610 EFLAGS: 00010293
RAX: ffffffff82170c43 RBX: 1ffff1100e413100 RCX: ffff88807e470000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff82170bc3 R09: 1ffffffff2038026
R10: dffffc0000000000 R11: fffffbfff2038027 R12: ffff888072098800
R13: ffffc90003ab77d0 R14: ffff8880720987b8 R15: dffffc0000000000
FS: 000055556dfec380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000564225f57310 CR3: 00000000770da000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2521 [inline]
udf_rename+0x969/0xe10 fs/udf/namei.c:867
vfs_rename+0xbdb/0xf00 fs/namei.c:5067
do_renameat2+0xd94/0x13f0 fs/namei.c:5224
__do_sys_rename fs/namei.c:5271 [inline]
__se_sys_rename fs/namei.c:5269 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5269
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f25e8587ad9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffdbb95b938 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007f25e8587ad9
RDX: 00007f25e8587ad9 RSI: 0000000020000f00 RDI: 00000000200000c0
RBP: 00007f25e85fb5f0 R08: 000055556dfed4c0 R09: 000055556dfed4c0
R10: 000055556dfed4c0 R11: 0000000000000246 R12: 00007ffdbb95b960
R13: 00007ffdbb95bb88 R14: 431bde82d7b634db R15: 00007f25e85d003b
</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 syzkaller@...glegroups.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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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
Powered by blists - more mailing lists