From: syzbot <syzbot+4c222134dc629d256ee8@syzkaller.appspotmail.com>
To: linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, lsahlber@redhat.com,
pc@manguebit.com, samba-technical@lists.samba.org,
sfr@canb.auug.org.au, sfrench@samba.org, sprasad@microsoft.com,
syzkaller-bugs@googlegroups.com, tom@talpey.com
Subject: [syzbot] linux-next build error (15)
Date: Wed, 28 Jun 2023 23:23:52 -0700 [thread overview]
Message-ID: <000000000000801b1a05ff3ebee0@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 8b14b70331aa Add linux-next specific files for 20230629
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11079dbf280000
kernel config: https://syzkaller.appspot.com/x/.config?x=83c17849d18e7a86
dashboard link: https://syzkaller.appspot.com/bug?extid=4c222134dc629d256ee8
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4c222134dc629d256ee8@syzkaller.appspotmail.com
fs/smb/client/cifs_debug.c:169:1: error: label at end of compound statement
---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change 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
reply other threads:[~2023-06-29 6:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000801b1a05ff3ebee0@google.com \
--to=syzbot+4c222134dc629d256ee8@syzkaller.appspotmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=pc@manguebit.com \
--cc=samba-technical@lists.samba.org \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox