diff options
| author | Philipp Zabel <p.zabel@pengutronix.de> | 2019-03-15 10:14:52 +0100 |
|---|---|---|
| committer | Sascha Hauer <s.hauer@pengutronix.de> | 2019-03-18 09:43:35 +0100 |
| commit | dc89bfe90223c12028d1f2c35d55564b7f46a326 (patch) | |
| tree | 02331c958294f85fa30550a7ca58e4ba29a9413f /Documentation/filesystems/pstore.rst | |
| parent | af85a0f8864e5888406bb13c3e3f99c5770959ca (diff) | |
| download | barebox-dc89bfe90223c12028d1f2c35d55564b7f46a326.tar.gz barebox-dc89bfe90223c12028d1f2c35d55564b7f46a326.tar.xz | |
pstore: ramoops: allow zapping invalid buffers in read-only mode
The FS_PSTORE_RAMOOPS_RO configuration option keeps barebox from zapping
(clearing and fixing header ecc) all ramoops buffers on initialization.
It also stops barebox from zapping invalid buffers. This causes issues
when the console writing code tries to use the uninitialized, invalid
console buffer. Therefore, allow barebox to zap invalid buffers, the
kernel will do so anyway if it finds broken buffers during its
initialization.
Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'Documentation/filesystems/pstore.rst')
0 files changed, 0 insertions, 0 deletions