public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+1bcef6d2f176c7d376fa@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	 sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com
Subject: [syzbot] linux-next build error (22)
Date: Tue, 15 Jul 2025 04:51:33 -0700	[thread overview]
Message-ID: <687640c5.a00a0220.3af5df.0004.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    f2b1f6a9f382 Add linux-next specific files for 20250715
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1057698c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b7b0e60e17dc5717
dashboard link: https://syzkaller.appspot.com/bug?extid=1bcef6d2f176c7d376fa
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

fs/bcachefs/super.c:2269:3: error: cannot jump from this goto statement to its label

---
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 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

                 reply	other threads:[~2025-07-15 11:51 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=687640c5.a00a0220.3af5df.0004.GAE@google.com \
    --to=syzbot+1bcef6d2f176c7d376fa@syzkaller.appspotmail.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=syzkaller-bugs@googlegroups.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