public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss•qualcomm.com>
To: Kent Overstreet <kent.overstreet@linux•dev>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	linux-bcachefs@vger•kernel.org
Subject: Build failure on next-20250801
Date: Sat, 2 Aug 2025 12:04:07 +0200	[thread overview]
Message-ID: <b390beb2-441f-4a3d-b53d-3f554b308be2@oss.qualcomm.com> (raw)

Hi, just hit the below on next-20250801

Reverting

4c3205637f1e ("bcachefs: CLASS(btree_iter)")
...
69c862491582 ("Revert "bcachefs: Convert bch2_bkey_get_mut() to
CLASS(btree_iter)"")

(mostly as dependencies for clean reverts)

gets it to build again.


In case that matters (which I believe it doesn't), I'm using clang
on x86, version 20.1.8


fs/bcachefs/backpointers.c:391:7: error: cannot jump from this goto statement to its label
  391 |                 if (fsck_err(trans, backpointer_to_missing_device,
      |                     ^
fs/bcachefs/error.h:140:2: note: expanded from macro 'fsck_err'
  140 |         __fsck_err(c, FSCK_CAN_FIX|FSCK_CAN_IGNORE, _err_type, __VA_ARGS__)
      |         ^
fs/bcachefs/error.h:117:26: note: expanded from macro '__fsck_err'
  117 | #define __fsck_err(...)         fsck_err_wrap(bch2_fsck_err(__VA_ARGS__))
      |                                 ^
fs/bcachefs/error.h:111:3: note: expanded from macro 'fsck_err_wrap'
  111 |                 goto fsck_err;                                          \
      |                 ^
fs/bcachefs/backpointers.c:398:20: note: jump bypasses initialization of variable with __attribute__((cleanup))
  398 |         CLASS(btree_iter, alloc_iter)(trans, BTREE_ID_alloc, bucket, 0);
      |                           ^
1 error generated.
make[4]: *** [scripts/Makefile.build:287: fs/bcachefs/backpointers.o] Błąd 1
make[4]: *** Oczekiwanie na niezakończone zadania....
fs/bcachefs/alloc_background.c:2097:7: error: cannot jump from this goto statement to its label
 2097 |                 if (fsck_err(trans, lru_entry_to_invalid_bucket,
      |                     ^
fs/bcachefs/error.h:140:2: note: expanded from macro 'fsck_err'
  140 |         __fsck_err(c, FSCK_CAN_FIX|FSCK_CAN_IGNORE, _err_type, __VA_ARGS__)
      |         ^
fs/bcachefs/error.h:117:26: note: expanded from macro '__fsck_err'
  117 | #define __fsck_err(...)         fsck_err_wrap(bch2_fsck_err(__VA_ARGS__))
      |                                 ^
fs/bcachefs/error.h:111:3: note: expanded from macro 'fsck_err_wrap'
  111 |                 goto fsck_err;                                          \
      |                 ^
fs/bcachefs/alloc_background.c:2107:20: note: jump bypasses initialization of variable with __attribute__((cleanup))
 2107 |         CLASS(btree_iter, alloc_iter)(trans, BTREE_ID_alloc, bucket, BTREE_ITER_cached);
      |                           ^
1 error generated.


Konrad

             reply	other threads:[~2025-08-02 10:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-02 10:04 Konrad Dybcio [this message]
2025-08-02 15:30 ` Build failure on next-20250801 Kent Overstreet

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=b390beb2-441f-4a3d-b53d-3f554b308be2@oss.qualcomm.com \
    --to=konrad.dybcio@oss$(echo .)qualcomm.com \
    --cc=kent.overstreet@linux$(echo .)dev \
    --cc=linux-bcachefs@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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