From: "John Stoffel" <john@stoffel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs for v6.7
Date: Tue, 31 Oct 2023 17:48:39 -0400 [thread overview]
Message-ID: <25921.30263.150556.245226@quad.stoffel.home> (raw)
Using latest HEAD from linux git (commit
5a6a09e97199d6600d31383055f9d43fbbcbe86f (HEAD -> master,
origin/master, origin/HEAD), and the following config, I get this
failure when compiling on x86_64 Debian Bullseye (11):
CC fs/bcachefs/btree_io.o
In file included from fs/bcachefs/btree_io.c:11:
fs/bcachefs/btree_io.c: In function ‘bch2_btree_post_write_cleanup’:
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];
| ^~~~~
In file included from fs/bcachefs/btree_io.c:11:
fs/bcachefs/btree_io.c: In function ‘bch2_btree_init_next’:
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];
| ^~~~~
cc1: all warnings being treated as errors
make[4]: *** [scripts/Makefile.build:243: fs/bcachefs/btree_io.o] Error 1
make[3]: *** [scripts/Makefile.build:480: fs/bcachefs] Error 2
make[2]: *** [scripts/Makefile.build:480: fs] Error 2
make[1]: *** [/local/src/kernel/git/linux/Makefile:1913: .] Error 2
make: *** [Makefile:234: __sub-make] Error 2
My .config looks like this for BCACHEFS:
$ grep BCACHEFS .config
CONFIG_BCACHEFS_FS=y
CONFIG_BCACHEFS_QUOTA=y
CONFIG_BCACHEFS_POSIX_ACL=y
CONFIG_BCACHEFS_DEBUG_TRANSACTIONS=y
CONFIG_BCACHEFS_DEBUG=y
CONFIG_BCACHEFS_TESTS=y
# CONFIG_BCACHEFS_LOCK_TIME_STATS is not set
# CONFIG_BCACHEFS_NO_LATENCY_ACCT is not set
next reply other threads:[~2023-10-31 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 21:48 John Stoffel [this message]
2023-10-31 22:11 ` Kent Overstreet
2023-10-31 22:17 ` John Stoffel
-- strict thread matches above, loose matches on Subject: below --
2023-10-30 14:55 Kent Overstreet
2023-10-30 23:50 ` pr-tracker-bot
2023-10-31 12:47 ` Geert Uytterhoeven
2023-10-31 14:45 ` Kent Overstreet
2023-10-31 15:00 ` Geert Uytterhoeven
2023-11-01 15:02 ` Geert Uytterhoeven
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=25921.30263.150556.245226@quad.stoffel.home \
--to=john@stoffel.org \
--cc=geert@linux-m68k.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®