| commit | 170e34712002eecaaaf115209b5d667b7dea99d9 | [log] [tgz] |
|---|---|---|
| author | Naoya Tezuka <naoyatezuka@chromium.org> | Fri Jun 20 15:28:22 2025 +0900 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 03 20:07:54 2025 -0700 |
| tree | a4d841089c7c8352670a6dcddd885d813fd37ec3 | |
| parent | 89ac383d586be7d14b9c07e23ed049a8b6e97c7f [diff] |
FROMGIT: platform/chrome: chromeos_pstore: Add ecc_size module parameter On ChromiumOS devices, the `ecc_size` is set to 0 (check dmesg | grep ecc to see `ecc: 0`): this disables ECC for ramoops region, even when `ramoops.ecc=1` is given to kernel command line parameter. Introduce `ecc_size` module parameter to provide a method to turn on ECC for ramoops and set different values of ecc_size per devices. A large `ecc_size` value can cause a kernel panic due to a constraint in Reed-Solomon code library. The validation for this constraint should belong to the common pstore RAM layer, not in each individual driver. So this check is handled by a separate patch [1]. [1] https://lore.kernel.org/lkml/20250620054757.1006729-1-naoyatezuka@chromium.org Signed-off-by: Naoya Tezuka <naoyatezuka@chromium.org> Link: https://lore.kernel.org/r/20250620062822.1018798-1-naoyatezuka@chromium.org Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org> (cherry picked from commit 545daf90910ec83e167cf3fbcc31fcf5467432b8 https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next) BUG=b:413292019 TEST=deploy to rammus with `chromeos_pstore.ecc_size=4` argument \ trigger kernel crash with key combo \ confirm ecc is turned on from cosnole-ramoops-0 Change-Id: I27728c987aded1e0b4f8effe49a055e7c92ce52a Signed-off-by: Naoya Tezuka <naoyatezuka@google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/6697043 Reviewed-by: Tzung-Bi Shih <tzungbi@chromium.org> Reviewed-by: Sean Paul <sean@poorly.run>