Rust version policy
The kernel documents the minimal requirements to compile it. However, in the case of Rust, currently we only support a single stable version: newer versions are allowed for convenience (with a warning from the build system), but they may or may not work. Older versions are disallowed.
The reason is that we cannot guarantee newer Rust versions will work due to the unstable features in use. Removing the need for them is a priority in order to be able to eventually declare a minimum Rust version for the kernel.
Before a minimum version can be declared
It remains to be decided how often the Rust version upgrades will land. Ideally we would track the latest Rust release, but it remains to be seen how other kernel developers feel about it.
On top of that, if the
klint support is merged and starts to be routinely used, then we will also need to be mindful of its schedule.
After a minimum version is declared
If we follow a similar model to the GCC and LLVM support in the kernel (which is likely), then we will not track the latest Rust release (i.e. as a minimum), though how wide the window will be remains to be seen. It is possible we may start with a small window and then widen it, similar to what was originally decided for the LLVM support in the kernel.
Please do not submit patches to upgrade the Rust version. If you want to discuss upgrading the Rust version in the kernel, then please contact us.
We are looking for feedback from Linux distributions, companies and other users and maintainers of downstream kernel releases.
In particular, it would be useful to know:
What versions/policy would work best your distribution/company.
If the kernel cannot satisfy exactly that (which is likely, given the current constraints), whether you would prefer to maintain a given compiler version for a while or to backport support from a newer version from mainline.