mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	regressions@lists.linux.dev
Subject: mainline build failure due to 5cfd69775eb5 ("bcachefs: Array bounds fixes")
Date: Tue, 31 Oct 2023 22:15:09 +0000	[thread overview]
Message-ID: <ZUF8bYTl5SBlbBBJ@debian> (raw)

Hi All,

The latest mainline kernel branch fails to build arm64 allmodconfig
with a native build on an arm64 host with the error:

In file included from fs/bcachefs/btree_io.c:11:
fs/bcachefs/btree_update_interior.h: In function 'want_new_bset':
fs/bcachefs/btree_update_interior.h:274:36: error: array subscript 0 is outside the bounds of an interior zero-length array 'struct bkey_packed[0]' [-Werror=zero-length-bounds]
  274 |   __bch_btree_u64s_remaining(c, b, &bne->keys.start[0]);
      |                                    ^~~~~~~~~~~~~~~~~~~
In file included from fs/bcachefs/bcachefs.h:206,
                 from fs/bcachefs/btree_io.c:3:
fs/bcachefs/bcachefs_format.h:2344:21: note: while referencing 'start'
 2344 |  struct bkey_packed start[0];
      |                     ^~~~~

git bisect pointed to 5cfd69775eb5 ("bcachefs: Array bounds fixes").

I will be happy to test any patch or provide any extra log if needed.

#regzbot introduced: 5cfd69775eb5460ef78bb5034a37eb0dc52ab65d

-- 
Regards
Sudip

             reply	other threads:[~2023-10-31 22:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 22:15 Sudip Mukherjee (Codethink) [this message]
2023-10-31 22:24 ` Kent Overstreet
2023-11-01  5:18   ` Sudip Mukherjee
2023-11-01  7:24     ` Linux regression tracking (Thorsten Leemhuis)

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=ZUF8bYTl5SBlbBBJ@debian \
    --to=sudipm.mukherjee@gmail.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®