user/sven/linux.git/include/linux/pstore.h, branch v4.19.43

pstore/ram: Correctly calculate usable PRZ bytes

2018-12-17T08:24:39Z

[ Upstream commit 89d328f637b9904b6d4c9af73c8a608b8dd4d6f8 ] The actual number of bytes stored in a PRZ is smaller than the bytes requested by platform data, since there is a header on each PRZ. Additionally, if ECC is enabled, there are trailing bytes used as well. Normally this mismatch doesn't matter since PRZs are circular buffers and the leading "overflow" bytes are just thrown away. However, in the case of a compressed record, this rather badly corrupts the results. This corruption was visible with "ramoops.mem_size=204800 ramoops.ecc=1". Any stored crashes would not be uncompressable (producing a pstorefs "dmesg-*.enc.z" file), and triggering errors at boot: [ 2.790759] pstore: crypto_comp_decompress failed, ret = -22! Backporting this depends on commit 70ad35db3321 ("pstore: Convert console write to use ->write_buf") Reported-by: Joel Fernandes Fixes: b0aad7a99c1d ("pstore: Add compression support to pstore") Signed-off-by: Kees Cook Reviewed-by: Joel Fernandes (Google) Signed-off-by: Sasha Levin

pstore: Convert internal records to timespec64

2018-06-05T23:57:31Z

This prepares pstore for converting the VFS layer to timespec64. Signed-off-by: Kees Cook Signed-off-by: Deepa Dinamani

pstore: Populate pstore record->time field

2017-05-31T17:13:44Z

The current time will be initially available in the record->time field for all pstore_read() and pstore_write() calls. Backends can either update the field during read(), or use the field during write() instead of fetching time themselves. Signed-off-by: Kees Cook

pstore: Remove write_buf() callback

2017-03-07T22:01:02Z

Now that write() and write_buf() are functionally identical, this removes write_buf(), and renames write_buf_user() to write_user(). Additionally adds sanity-checks for pstore_info's declared functions and flags at registration time. Signed-off-by: Kees Cook

pstore: Replace arguments for write_buf_user() API

2017-03-07T22:01:01Z

Removes argument list in favor of pstore record, though the user buffer remains passed separately since it must carry the __user annotation. Signed-off-by: Kees Cook

pstore: Replace arguments for write_buf() API

2017-03-07T22:01:01Z

As with the other API updates, this removes the long argument list in favor of passing a single pstore recaord. Signed-off-by: Kees Cook

pstore: Replace arguments for erase() API

2017-03-07T22:01:00Z

This removes the argument list for the erase() callback and replaces it with a pointer to the backend record details to be removed. Signed-off-by: Kees Cook

pstore: Replace arguments for write() API

2017-03-07T22:00:56Z

Similar to the pstore_info read() callback, there were too many arguments. This switches to the new struct pstore_record pointer instead. This adds "reason" and "part" to the record structure as well. Signed-off-by: Kees Cook

pstore: Replace arguments for read() API

2017-03-07T22:00:55Z

The argument list for the pstore_read() interface is unwieldy. This changes passes the new struct pstore_record instead. The erst backend was already doing something similar internally. Signed-off-by: Kees Cook

pstore: Extract common arguments into structure

2017-03-07T22:00:53Z

The read/mkfile pair pass the same arguments and should be cleared between calls. Move to a structure and wipe it after every loop. Signed-off-by: Kees Cook