From: syzbot <syzbot+eeb58d2197d88720a228@syzkaller.appspotmail.com>
To: bharathsm@microsoft.com, linux-cifs@vger.kernel.org,
linux-kernel@vger.kernel.org, pc@manguebit.org,
ronniesahlberg@gmail.com, samba-technical@lists.samba.org,
sfrench@samba.org, sprasad@microsoft.com,
syzkaller-bugs@googlegroups.com, tom@talpey.com
Subject: [syzbot] [cifs?] WARNING in smb2_add_credits
Date: Fri, 31 Jul 2026 17:35:35 -0700 [thread overview]
Message-ID: <6a6d3f57.6ce73036.24301b.000f.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: f5098b6bae76 Linux 7.2-rc5
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17d5d1b9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=145fa60d73086782
dashboard link: https://syzkaller.appspot.com/bug?extid=eeb58d2197d88720a228
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12299632580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2113dcf433f6/disk-f5098b6b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/413e673b7de4/vmlinux-f5098b6b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fc40c1b83e80/bzImage-f5098b6b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+eeb58d2197d88720a228@syzkaller.appspotmail.com
CIFS: VFS: \\127.0.0.1 Error -104 sending data on socket to server
------------[ cut here ]------------
server->in_flight == 0
WARNING: fs/smb/client/smb2ops.c:104 at smb2_add_credits+0x1213/0x1790 fs/smb/client/smb2ops.c:104, CPU#0: syz.2.443/8120
Modules linked in:
CPU: 0 UID: 0 PID: 8120 Comm: syz.2.443 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:smb2_add_credits+0x1213/0x1790 fs/smb/client/smb2ops.c:104
Code: c6 e8 21 ea b5 fe 84 db 0f 85 0a fb ff ff e8 04 f0 b5 fe 48 8d 3d ad 9f d5 0d 67 48 0f b9 3a e9 f4 fa ff ff e8 ee ef b5 fe 90 <0f> 0b 90 0f b6 05 87 d6 b5 0d 31 ff 89 c6 88 44 24 28 e8 e6 e9 b5
RSP: 0018:ffffc90005cbf2d8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88805d5ee300 RCX: ffffffff835460db
RDX: ffff88801c79ca80 RSI: ffffffff83547052 RDI: ffff88801c79ca80
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90005cbf518
R13: 0000000000000200 R14: 0000000000000002 R15: ffff88805d5ee000
FS: 00007f783f8496c0(0000) GS:ffff888123ddc000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000077f4543a020 CR3: 000000002b566000 CR4: 00000000003526f0
Call Trace:
<TASK>
add_credits fs/smb/client/cifsglob.h:894 [inline]
compound_send_recv+0x1030/0x2a10 fs/smb/client/transport.c:979
---
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@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 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
next reply other threads:[~2026-08-01 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 0:35 syzbot [this message]
2026-08-05 0:00 ` [syzbot] [cifs?] WARNING in smb2_add_credits syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a6d3f57.6ce73036.24301b.000f.GAE@google.com \
--to=syzbot+eeb58d2197d88720a228@syzkaller.appspotmail.com \
--cc=bharathsm@microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=sprasad@microsoft.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tom@talpey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.