diff options
| author | Daniel Micay <danielmicay@gmail.com> | 2021-10-08 01:34:26 -0400 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2021-10-08 01:34:26 -0400 |
| commit | 1e07afe0aee6c3ffd28ee280496fff1c861bd338 (patch) | |
| tree | e9d97d04321d4b1007e118682bb22c1e2592f8d5 | |
| parent | 5c21e88083ccff97f494365034d711c4985a6fb9 (diff) | |
clarify upcoming full 2021-10-05 patch level
| -rw-r--r-- | static/releases.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/static/releases.html b/static/releases.html index e6f3256f..3b08f0ad 100644 --- a/static/releases.html +++ b/static/releases.html @@ -471,7 +471,7 @@ <p>Changes since the 2021100502 release:</p> <ul> - <li>backport of the Android 12 GrapheneOS Pixel kernels to Android 11 GrapheneOS including the full 2021-10-05 kernel patch level</li> + <li>backport of the Android 12 GrapheneOS Pixel kernels to Android 11 GrapheneOS including the full 2021-10-05 kernel patch level (full set of fixes for firmware and userspace will be provided by the upcoming release of Android 12 for Pixels)</li> <li>kernel (Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, Pixel 5, Pixel 5a): rebase onto Android 12 SP1A.210812.016 kernel releases</li> <li>kernel (Pixel 4, Pixel 4 XL, Pixel 5, Pixel 5a): temporarily disable unnecessary DEBUG_NOTIFIERS feature (type-based CFI obsoletes it as a security feature) due to an incompatibility with the updated Android 12 kernel LLVM toolchain (discovered issue is benign but we'll be fixing it in a future release)</li> <li>kernel (Pixel 4, Pixel 4 XL, Pixel 4a): use zero-based filling for stack initialization like the other devices</li> @@ -491,7 +491,7 @@ <ul> <li>full 2021-10-01 security patch level</li> - <li>partial 2021-10-05 security patch level (full set of fixes will be provided by the upcoming release of Android 12 release for Pixels)</li> + <li>partial 2021-10-05 security patch level (full set of fixes will be provided by the upcoming release of Android 12 for Pixels)</li> <li>rebased onto RQ3A.211001.001 and RD2A.211001.002 releases</li> <li>drop our downstream workaround for use-after-free vulnerability in init now that the issue we reported is fixed upstream</li> </ul> |