Skip to content

Mirror rust-lang/rust kernel artifacts used by CI jobs#41

Closed
jieyouxu wants to merge 1 commit into
rust-lang:mainfrom
jieyouxu:jieyouxu/hotfix/kernel-artifacts
Closed

Mirror rust-lang/rust kernel artifacts used by CI jobs#41
jieyouxu wants to merge 1 commit into
rust-lang:mainfrom
jieyouxu:jieyouxu/hotfix/kernel-artifacts

Conversation

@jieyouxu

@jieyouxu jieyouxu commented Jul 4, 2026

Copy link
Copy Markdown
Member

Summary

Part of rust-lang/rust#158718.
See #t-infra > kernel.org is borked.

Currently rust-lang/rust CI is borked because:

  1. armhf-gnu directly tries to download kernel v4.x artifacts from kernel.org mirror, and
  2. certain dist-* jobs tries to download kernel v3.x and v4.x artifacts from kernel.org mirror 1.

However, kernel.org mirror sync infra has an active incident (ref: https://status.linuxfoundation.org/incidents/3y1k8b4ky71t) where not all files are available. In particular, v3.x and v4.x kernel artifacts are not recovered yet as of time of writing (check https://mirrors.edge.kernel.org/pub/linux/kernel/).

This PR tries to seed v3.x, v4.x kernel artifacts from elsewhere, notably from Way Back Machine and the partial/outdated University of Science and Technology of China (USTC) mirror which seemingly haven't synced with upstream yet.

Which kernel versions are needed?

  • For armhf-gnu, it directly tries to fetch 4.14.320 (ref). In this PR, we will use the latest 4.14.336 of 4.14.x series instead.
  • For the other dist-* jobs, they indirectly fetch 3.2.x, 3.10.x, 4.4.x, 4.19.x, 4.20.x, 5.19.x kernel releases from the kernel archives, through crosstool-ng usages.
Query the defconfigs
$ find src/ci/docker/host-* -type f -name "*.defconfig" | xargs grep -H "^CT_LINUX_V_"
src/ci/docker/host-x86_64/dist-powerpc64le-linux-gnu/powerpc64le-unknown-linux-gnu.defconfig:CT_LINUX_V_3_10=y
src/ci/docker/host-x86_64/dist-mipsel-linux/mipsel-linux-gnu.defconfig:CT_LINUX_V_4_4=y
src/ci/docker/host-x86_64/dist-i586-gnu-i586-i686-musl/i586-linux-gnu.defconfig:CT_LINUX_V_3_2=y
src/ci/docker/host-x86_64/dist-mips-linux/mips-linux-gnu.defconfig:CT_LINUX_V_4_4=y
src/ci/docker/host-x86_64/dist-arm-linux-gnueabi/arm-linux-gnueabi.defconfig:CT_LINUX_V_3_2=y
src/ci/docker/host-x86_64/dist-armv7-linux/armv7-linux-gnueabihf.defconfig:CT_LINUX_V_3_2=y
src/ci/docker/host-x86_64/dist-s390x-linux/s390x-linux-gnu.defconfig:CT_LINUX_V_3_2=y
src/ci/docker/host-x86_64/dist-powerpc64le-linux-musl/powerpc64le-unknown-linux-musl.defconfig:CT_LINUX_V_4_19=y
src/ci/docker/host-x86_64/dist-mips64el-linux/mips64el-linux-gnu.defconfig:CT_LINUX_V_4_4=y
src/ci/docker/host-x86_64/dist-loongarch64-linux/loongarch64-unknown-linux-gnu.defconfig:CT_LINUX_V_5_19=y
src/ci/docker/host-x86_64/dist-powerpc-linux/powerpc-linux-gnu.defconfig:CT_LINUX_V_3_2=y
src/ci/docker/host-x86_64/dist-powerpc64-linux-musl/powerpc64-unknown-linux-musl.defconfig:CT_LINUX_V_4_19=y
src/ci/docker/host-x86_64/dist-powerpc64-linux-gnu/powerpc64-linux-gnu.defconfig:CT_LINUX_V_3_2=y
src/ci/docker/host-x86_64/dist-riscv64-linux/riscv64-unknown-linux-gnu.defconfig:CT_LINUX_V_4_20=y
src/ci/docker/host-x86_64/dist-mips64-linux/mips64-linux-gnu.defconfig:CT_LINUX_V_4_4=y
src/ci/docker/host-x86_64/dist-loongarch64-musl/loongarch64-unknown-linux-musl.defconfig:CT_LINUX_V_5_19=y
src/ci/docker/host-x86_64/dist-armhf-linux/arm-linux-gnueabihf.defconfig:CT_LINUX_V_3_2=y

$ find src/ci/docker/host-* -type f -name "*.defconfig" | xargs grep -h "^CT_LINUX_V_" | sort -u
CT_LINUX_V_3_10=y
CT_LINUX_V_3_2=y
CT_LINUX_V_4_19=y
CT_LINUX_V_4_20=y
CT_LINUX_V_4_4=y
CT_LINUX_V_5_19=y

What are the exact kernel versions available from alternative sources?

Using https://en.wikipedia.org/wiki/Linux_kernel_version_history and cross-referencing with a slower-updated kernel.org mirror hosted by USTC (https://mirrors.ustc.edu.cn/kernel.org/linux/kernel/v3.x/, https://mirrors.ustc.edu.cn/kernel.org/linux/kernel/v4.x/, https://mirrors.ustc.edu.cn/kernel.org/linux/kernel/v5.x/):

Kernel LTS release series Last release in the series Notes
4.2.* 3.2.102  
3.10.* 3.10.108  
4.4.* 4.4.302 Not using SLTS 4.4.302-cip103 release, just the normal one
4.14.* 4.14.336 For armhf-gnu specifically.
4.19.* 4.19.325 Not using SLTS 4.19.325-cip124 release, just the normal one
4.20.* 4.20.17  
6.19.* 5.19.17  

However not the latest {.tar.xz, .tar.sign} pairs are available in either the Wayback Machine archive or USTC mirror, so we have to make do with the latest versions in each release series I could find:

Latest kernel release in series Actual kernel release found .tar.xz artifact URL .tar.sign artifact signature URL Notes
3.2.102 3.2.86 http://mirrors.ustc.edu.cn/kernel.org/linux/kernel/v3.x/linux-3.2.86.tar.xz http://mirrors.ustc.edu.cn/kernel.org/linux/kernel/v3.x/linux-3.2.86.tar.sign Couldn't find newer ones from either USTC mirror or WBM with both {.tar.xz,.tar.sign}.
3.10.108 3.10.105 https://mirrors.ustc.edu.cn/kernel.org/linux/kernel/v3.x/linux-3.10.105.tar.xz https://mirrors.ustc.edu.cn/kernel.org/linux/kernel/v3.x/linux-3.10.105.tar.sign Couldn't find newer ones from either USTC mirror or WBM with both {.tar.xz,.tar.sign}. WBM seems to have no signatures for 3.10.* series at all?
4.4.302 4.4.302 https://web.archive.org/web/20240515072011/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.4.302.tar.xz https://web.archive.org/web/20240515072011/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.4.302.tar.sign  
4.14.336 4.14.336 https://web.archive.org/web/20240515072334/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.14.336.tar.xz https://web.archive.org/web/20240515072334/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.14.336.tar.sign For armhf-gnu specifically.
4.19.325 4.19.312 https://web.archive.org/web/20240507062408/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.19.312.tar.xz https://web.archive.org/web/20240507062408/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.19.312.tar.sign Couldn't find newer ones from either USTC mirror or WBM with both {.tar.xz,.tar.sign}.
4.20.17 4.20.17 https://web.archive.org/web/20240507093811/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.20.17.tar.xz https://web.archive.org/web/20240507093811/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.20.17.tar.sign  
5.19.17 5.19.17 https://www.kernel.org/pub/linux/kernel/v5.x/linux-5.19.17.tar.xz https://www.kernel.org/pub/linux/kernel/v5.x/linux-5.19.17.tar.sign Already available on official kernel mirror.

Verify attestation

Fetch kernel PGP signatures

$ git clone https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git
$ cd pgpkeys
$ grep -il "torvalds" keys/*.asc
keys/79BE3E4300411886.asc
$ grep -il "Greg Kroah-Hartman" keys/*.asc
keys/38DBBDC86092693E.asc
$ gpg --import keys/79BE3E4300411886.asc keys/38DBBDC86092693E.asc

Check archive signatures

Check tar.xz signatures
$ xz -cd linux-3.2.86.tar.xz | gpg --verify linux-3.2.86.tar.sign -
gpg: Signature made Mon Feb 27 14:57:09 2017 CST
gpg:                using RSA key 647F28654894E3BD457199BE38DBBDC86092693E
gpg: Good signature from "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@kernel.org>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@linuxfoundation.org>" [unknown]
$ xz -cd linux-3.10.105.tar.xz | gpg --verify linux-3.10.105.tar.sign -
gpg: Signature made Fri Feb 10 18:51:01 2017 CST
gpg:                using RSA key 647F28654894E3BD457199BE38DBBDC86092693E
gpg: Good signature from "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@kernel.org>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@linuxfoundation.org>" [unknown]
$ xz -cd linux-4.4.302.tar.xz | gpg --verify linux-4.4.302.tar.sign -
gpg: Signature made Thu Feb  3 16:29:04 2022 CST
gpg:                using RSA key 647F28654894E3BD457199BE38DBBDC86092693E
gpg: Good signature from "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@kernel.org>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@linuxfoundation.org>" [unknown]
$ xz -cd linux-4.19.312.tar.xz | gpg --verify linux-4.19.312.tar.sign -
gpg: Signature made Sat Apr 13 18:51:17 2024 CST
gpg:                using RSA key 647F28654894E3BD457199BE38DBBDC86092693E
gpg: Good signature from "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@kernel.org>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@linuxfoundation.org>" [unknown]
$ xz -cd linux-4.20.17.tar.xz | gpg --verify linux-4.20.17.tar.sign -
gpg: Signature made Tue Mar 19 20:12:35 2019 CST
gpg:                using RSA key 647F28654894E3BD457199BE38DBBDC86092693E
gpg: Good signature from "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@kernel.org>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@linuxfoundation.org>" [unknown]
$ xz -cd linux-5.19.17.tar.xz | gpg --verify linux-5.19.17.tar.sign -
gpg: Signature made Mon Oct 24 16:00:22 2022 CST
gpg:                using RSA key 647F28654894E3BD457199BE38DBBDC86092693E
gpg: Good signature from "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@kernel.org>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@linuxfoundation.org>" [unknown]

For the armhf-gnu one:

$ xz -cd linux-4.14.336.tar.xz | gpg --verify linux-4.14.336.tar.sign -
gpg: Signature made Wed Jan 10 21:46:33 2024 CST
gpg:                using RSA key 647F28654894E3BD457199BE38DBBDC86092693E
gpg: Good signature from "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@kernel.org>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@linuxfoundation.org>" [unknown]

Calculate SHA of the archives to compare to ci-mirrors SHA256 in this PR

Command
$ ls -l1 *.tar.xz | xargs sha256
SHA256 (linux-3.10.105.tar.xz) = 1c5bcc129cbbe2f665e8446b4c2fdbec0ec5f2b5d40495abfba13bbf66ac699c
SHA256 (linux-3.2.86.tar.xz) = c5a4494cdf27421d8cf05039937f7a0410ec83b649730d46a01beef6257c72d9
SHA256 (linux-4.14.336.tar.xz) = 0820fdb7971c6974338081c11fbf2dc869870501e7bdcac4d0ed58ba1f57b61c
SHA256 (linux-4.19.312.tar.xz) = a394fa5ffe321ee43dae9cccc724572f49fbb289875d39ea695adf712e51f74a
SHA256 (linux-4.20.17.tar.xz) = d011245629b980d4c15febf080b54804aaf215167b514a3577feddb2495f8a3e
SHA256 (linux-4.4.302.tar.xz) = 35017bb40b604e0b577fc2b87e727632b46608a2ba3a4f5858b9177f58f376b3
SHA256 (linux-5.19.17.tar.xz) = c93bb384a97ad1f0a4f18e442ce0291242722f78023eca658b22344541f09489
Filename SHA256
linux-3.2.86.tar.xz c5a4494cdf27421d8cf05039937f7a0410ec83b649730d46a01beef6257c72d9
linux-3.10.105.tar.xz 1c5bcc129cbbe2f665e8446b4c2fdbec0ec5f2b5d40495abfba13bbf66ac699c
linux-4.4.302.tar.xz 35017bb40b604e0b577fc2b87e727632b46608a2ba3a4f5858b9177f58f376b3
linux-4.14.336.tar.xz 0820fdb7971c6974338081c11fbf2dc869870501e7bdcac4d0ed58ba1f57b61c
linux-4.19.312.tar.xz a394fa5ffe321ee43dae9cccc724572f49fbb289875d39ea695adf712e51f74a
linux-4.20.17.tar.xz d011245629b980d4c15febf080b54804aaf215167b514a3577feddb2495f8a3e
linux-5.19.17.tar.xz c93bb384a97ad1f0a4f18e442ce0291242722f78023eca658b22344541f09489

ci-mirrors tool invocations

Invocations
$ cargo run -- add-file https://mirrors.ustc.edu.cn/kernel.org/linux/kernel/v3.x/linux-3.2.86.tar.xz --path=rustc/kernel/linux-3.2.86.tar.xz --toml-file="files/rustc/kernel.toml" --license="GPL-2.0"
$ cargo run -- add-file https://mirrors.ustc.edu.cn/kernel.org/linux/kernel/v3.x/linux-3.10.105.tar.xz --path=rustc/kernel/linux-3.10.105.tar.xz --toml-file="files/rustc/kernel.toml" --license="GPL-2.0"
$ cargo run -- add-file https://web.archive.org/web/20240515072011/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.4.302.tar.xz --path=rustc/kernel/linux-4.4.302.tar.xz --toml-file="files/rustc/kernel.toml" --license="GPL-2.0"
$ cargo run -- add-file https://web.archive.org/web/20240515072334/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.14.336.tar.xz --path=rustc/kernel/linux-4.14.336.tar.xz --toml-file="files/rustc/kernel.toml" --license="GPL-2.0"
$ cargo run -- add-file https://web.archive.org/web/20240507062408/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.19.312.tar.xz --path=rustc/kernel/linux-4.19.312.tar.xz --toml-file="files/rustc/kernel.toml" --license="GPL-2.0"
$ cargo run -- add-file https://web.archive.org/web/20240507093811/https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/linux-4.20.17.tar.xz --path=rustc/kernel/linux-4.20.17.tar.xz --toml-file="files/rustc/kernel.toml" --license="GPL-2.0"
$ cargo run -- add-file https://www.kernel.org/pub/linux/kernel/v5.x/linux-5.19.17.tar.xz --path=rustc/kernel/linux-5.19.17.tar.xz --toml-file="files/rustc/kernel.toml" --license="GPL-2.0"

Review notes

Important

The reviewer must double-check the attestation of the artifacts because they are directly used in dist-* jobs, which are CI jobs that we ship dist artifacts from.

Footnotes

  1. Add v5.x but those are already recovered.

@jieyouxu

jieyouxu commented Jul 4, 2026

Copy link
Copy Markdown
Member Author

Closing since we should source from official git exports: #t-infra > kernel.org is borked @ 💬

@jieyouxu jieyouxu closed this Jul 4, 2026
@jieyouxu
jieyouxu deleted the jieyouxu/hotfix/kernel-artifacts branch July 4, 2026 11:54
rust-bors Bot pushed a commit to rust-lang/rust that referenced this pull request Jul 4, 2026
Mirror kernel archives in `ci-mirrors` to not depend on currently unavailable kernel mirror sources



## Summary

(Tempoarily) closes #158718.
See [#t-infra > kernel.org is borked](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/kernel.2Eorg.20is.20borked/with/608182062).

Currently rust-lang/rust CI is borked because:

1. `armhf-gnu` directly tries to download kernel v4.x artifacts from kernel.org mirror, and
2. certain `dist-*` jobs tries to download kernel v3.x and v4.x artifacts from kernel.org mirror indirectly via crosstools-ng ("CT-NG") [^1].

[^1]: Add v5.x but those are already recovered.

However, kernel.org mirror sync infra has an active incident (ref: https://status.linuxfoundation.org/incidents/3y1k8b4ky71t) where not all files are available. In particular, v3.x and v4.x kernel artifacts are not recovered yet as of time of writing (check <https://mirrors.edge.kernel.org/pub/linux/kernel/>).

### Mitigation

This PR tries to mitigate this by using our own mirrored kernel artifacts from `ci-mirrors` (see rust-lang/ci-mirrors#41, rust-lang/ci-mirrors#42, rust-lang/ci-mirrors#43), such that `linux-$A.$B.$C.tar.gz` artifacts become available as search locations to CT-NG.

We carry a patch to CT-NG to use our own `ci-mirrors` artifact SHA256 checksums, the checksum mismatches are as far as we know due to compression setting differences (`ci-mirrors` source archives from <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/snapshot/>).

## Notes

- `armhf-gnu` still has artifacts from third-party mirrors/sources (busybox, ubuntu-base-22.04.2). Not in scope of this PR.
- It looks like `3.*` kernel series are considered obselete by CT-NG, and need `CT_OBSOLETE=y` config.
- CT-NG checks for known-good kernel versions and checksums against the provided mirror.

### CT-NG known good versions

Re. latest kernel versions in each release versus what CT-NG 1.28.0 considers a known good version w/ checksum:

Kernel LTS release series | Last release in the series | CT-NG 1.28.0 known good kernel version w/ checksum
-- | -- | --
3.2.* | 3.2.102 | **3.2.101**
3.10.* | 3.10.108 | 3.10.108
4.4.* | 4.4.302 | 4.4.302
4.19.* | 4.19.325 | 4.19.325
4.20.* | 4.20.17 | 4.20.17
5.19.* | 5.19.17 | **5.19.16**

(**Bold** CT-NG known good version indicates not latest in release series.)

### `ci-mirrors` kernal tarball SHA256 checksums

Refer to https://github.com/rust-lang/ci-mirrors/blob/b474b4bb35108dab668907172c858854f209c809/files/rustc/kernel.toml:

| **Kernel Version** | **SHA256**                                                         |
| ------------------ | ------------------------------------------------------------------ |
| 3.2.101            | `93e8391e029f131d5ba4b7ad76cc34b12f2c2244059604042f2297c4bde093f7` |
| 3.10.108           | `b1711610cf3faf7194156dacdb98c63c1b7ffd02377269d7f75df63d823ccbba` |
| 4.4.302            | `a22ceab143d40f511203265e5a70d6cc5ec39163cd54fa281346d19176f64451` |
| 4.19.325           | `8753443636e475b506e08abd40059ec9b84904a115d206014f0c856dfe13a25e` |
| 4.20.17            | `313b7bebb46084efbfcaf75f4ea6faf2e14c8cbc1711fcba483dc0a036c9acc1` |
| 5.19.16            | `bbf0ead65559250e0784c13d4f9716b7f917a1d3a4e00f671f3994cc6990bb02` |

---

try-job: armhf-gnu
try-job: dist-armhf-linux
try-job: dist-arm-linux-gnueabi
try-job: dist-powerpc64le-linux-musl
try-job: dist-loongarch64-musl
try-job: dist-riscv64-linux
try-job: dist-powerpc64le-linux-gnu
try-job: dist-powerpc64-linux-musl
try-job: dist-armv7-linux
try-job: dist-powerpc-linux
try-job: dist-loongarch64-linux
try-job: dist-s390x-linux
try-job: dist-i586-gnu-i586-i686-musl
try-job: dist-powerpc64-linux-gnu
rust-bors Bot pushed a commit to rust-lang/rust that referenced this pull request Jul 4, 2026
Mirror kernel archives in `ci-mirrors` to not depend on currently unavailable kernel mirror sources



## Summary

(Tempoarily) closes #158718.
See [#t-infra > kernel.org is borked](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/kernel.2Eorg.20is.20borked/with/608182062).

Currently rust-lang/rust CI is borked because:

1. `armhf-gnu` directly tries to download kernel v4.x artifacts from kernel.org mirror, and
2. certain `dist-*` jobs tries to download kernel v3.x and v4.x artifacts from kernel.org mirror indirectly via crosstools-ng ("CT-NG") [^1].

[^1]: Add v5.x but those are already recovered.

However, kernel.org mirror sync infra has an active incident (ref: https://status.linuxfoundation.org/incidents/3y1k8b4ky71t) where not all files are available. In particular, v3.x and v4.x kernel artifacts are not recovered yet as of time of writing (check <https://mirrors.edge.kernel.org/pub/linux/kernel/>).

### Mitigation

This PR tries to mitigate this by using our own mirrored kernel artifacts from `ci-mirrors` (see rust-lang/ci-mirrors#41, rust-lang/ci-mirrors#42, rust-lang/ci-mirrors#43), such that `linux-$A.$B.$C.tar.gz` artifacts become available as search locations to CT-NG.

We carry a patch to CT-NG to use our own `ci-mirrors` artifact SHA256 checksums, the checksum mismatches are as far as we know due to compression setting differences (`ci-mirrors` source archives from <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/snapshot/>).

## Notes

- `armhf-gnu` still has artifacts from third-party mirrors/sources (busybox, ubuntu-base-22.04.2). Not in scope of this PR.
- It looks like `3.*` kernel series are considered obselete by CT-NG, and need `CT_OBSOLETE=y` config.
- CT-NG checks for known-good kernel versions and checksums against the provided mirror.

### CT-NG known good versions

Re. latest kernel versions in each release versus what CT-NG 1.28.0 considers a known good version w/ checksum:

Kernel LTS release series | Last release in the series | CT-NG 1.28.0 known good kernel version w/ checksum
-- | -- | --
3.2.* | 3.2.102 | **3.2.101**
3.10.* | 3.10.108 | 3.10.108
4.4.* | 4.4.302 | 4.4.302
4.19.* | 4.19.325 | 4.19.325
4.20.* | 4.20.17 | 4.20.17
5.19.* | 5.19.17 | **5.19.16**

(**Bold** CT-NG known good version indicates not latest in release series.)

### `ci-mirrors` kernal tarball SHA256 checksums

Refer to https://github.com/rust-lang/ci-mirrors/blob/b474b4bb35108dab668907172c858854f209c809/files/rustc/kernel.toml:

| **Kernel Version** | **SHA256**                                                         |
| ------------------ | ------------------------------------------------------------------ |
| 3.2.101            | `93e8391e029f131d5ba4b7ad76cc34b12f2c2244059604042f2297c4bde093f7` |
| 3.10.108           | `b1711610cf3faf7194156dacdb98c63c1b7ffd02377269d7f75df63d823ccbba` |
| 4.4.302            | `a22ceab143d40f511203265e5a70d6cc5ec39163cd54fa281346d19176f64451` |
| 4.19.325           | `8753443636e475b506e08abd40059ec9b84904a115d206014f0c856dfe13a25e` |
| 4.20.17            | `313b7bebb46084efbfcaf75f4ea6faf2e14c8cbc1711fcba483dc0a036c9acc1` |
| 5.19.16            | `bbf0ead65559250e0784c13d4f9716b7f917a1d3a4e00f671f3994cc6990bb02` |

---

try-job: armhf-gnu
try-job: dist-armhf-linux
try-job: dist-arm-linux-gnueabi
try-job: dist-powerpc64le-linux-musl
try-job: dist-loongarch64-musl
try-job: dist-riscv64-linux
try-job: dist-powerpc64le-linux-gnu
try-job: dist-powerpc64-linux-musl
try-job: dist-armv7-linux
try-job: dist-powerpc-linux
try-job: dist-loongarch64-linux
try-job: dist-s390x-linux
try-job: dist-i586-gnu-i586-i686-musl
try-job: dist-powerpc64-linux-gnu
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant