From: Kent Overstreet <kent.overstreet@linux.dev>
To: pve-devel@lists.proxmox.com
Cc: Krzysztof Hajdamowicz <krzysztof@hajdamowicz.info>
Subject: Re: [PATCH pve-kernel] build: ship Rust artifacts for external modules
Date: Mon, 24 Aug 2026 12:52:03 -0500 [thread overview]
Message-ID: <aoyEw9yu7pq7B5q-@shelob> (raw)
In-Reply-To: <20260812162527.98882-1-krzysztof@hajdamowicz.info>
Late followup, because I only checked yesterday and noticed that the
testing on this patch was a snafu.
(_why_ would you send out a patch that you weren't able to successfully
test end to end yourself? I am still scratching my head on that one).
However - the patch is correct, the screwup was just trying to build
bcachefs with a different rustc than the kernel was built with - proxmox
kernels build with rustc from trixie-backports.
I've tested it end to end, and the patch is good and follows what Ubuntu
is doing:
Linux farm2-kvm 7.0.14-14-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-14 (2026-08-22T15:01Z)
CONFIG_RUSTC_VERSION_TEXT="rustc 1.94.1 (e408947bf 2026-03-25) (built from a source tarball)"
[5.383] bcachefs: loading out-of-tree module taints kernel.
[5.482] bcachefs: bch2_dirent_init() ...
vermagic: 7.0.14-14-pve SMP preempt mod_unload modversions
[5.574] starting version need_discard_by_journal_seq (1.38)
[5.574] Rust support enabled
[5.575] bcachefs (vdb): initializing new filesystem
[5.578] bcachefs (vdb): going read-write
... 64M O_DIRECT write, umount, remount, sha1sum -c OK, fsck clean
========= PASSED pve_module in 2s
TEST SUCCESS
As a reminder, every other distro is either shipping the Rust build
artifacts or supports reproducible kernel builds; this patch is
necessary for bcachefs to continue supporting Proxmox.
Cheers,
Kent
prev parent reply other threads:[~2026-08-25 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 16:25 [PATCH pve-kernel] build: ship Rust artifacts for external modules Krzysztof Hajdamowicz
2026-08-24 17:52 ` Kent Overstreet [this message]
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=aoyEw9yu7pq7B5q-@shelob \
--to=kent.overstreet@linux.dev \
--cc=krzysztof@hajdamowicz.info \
--cc=pve-devel@lists.proxmox.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