Changes in Makefile

17639f67 - pstore/blk: Introduce backend for block devices

Wed, 25 Mar 2020 08:54:57 +0000

pstore/blk: Introduce backend for block devicespstore/blk is similar to pstore/ram, but uses a block device as thestorage rather than persistent ram.The pstore/blk backend solves two common use-cases that used to precludeusing pstore/ram:- not all devices have a battery that could be used to persist regular RAM across power failures.- most embedded intelligent equipment have no persistent ram, which increases costs, instead preferring cheaper solutions, like block devices.pstore/blk provides separate configurations for the end user and for theblock drivers. User configuration determines how pstore/blk operates, suchas record sizes, max kmsg dump reasons, etc. These can be set by Kconfigand/or module parameters, but module parameter have priority over Kconfig.Driver configuration covers all the details about the target block device,such as total size of the device and how to perform read/write operations.These are provided by block drivers, calling pstore_register_blkdev(),including an optional panic_write callback used to bypass regular IOAPIs in an effort to avoid potentially destabilized kernel code duringa panic.Signed-off-by: WeiXiong Liao Link: https://lore.kernel.org/lkml/20200511233229.27745-3-keescook@chromium.org/Co-developed-by: Kees Cook Signed-off-by: Kees Cook List of files: /linux-6.15/fs/pstore/Makefile

d26c3321 - pstore/zone: Introduce common layer to manage storage zones

Wed, 25 Mar 2020 08:54:56 +0000

pstore/zone: Introduce common layer to manage storage zonesImplement a common set of APIs needed to support pstore storage zones,based on how ramoops is designed. This will be used by pstore/blk withthe intention of migrating pstore/ram in the future.Signed-off-by: WeiXiong Liao Link: https://lore.kernel.org/lkml/20200511233229.27745-2-keescook@chromium.org/Co-developed-by: Kees Cook Signed-off-by: Kees Cook List of files: /linux-6.15/fs/pstore/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/fs/pstore/Makefile

ee1d2674 - pstore: add pstore unregister

Tue, 20 Oct 2015 07:39:03 +0000

pstore: add pstore unregisterpstore doesn't support unregistering yet. It was marked as TODO.This patch adds some code to fix it: 1) Add functions to unregister kmsg/console/ftrace/pmsg. 2) Add a function to free compression buffer. 3) Unmap the memory and free it. 4) Add a function to unregister pstore filesystem.Signed-off-by: Geliang Tang Acked-by: Kees Cook [Removed __exit annotation from ramoops_remove(). Reported by Arnd Bergmann]Signed-off-by: Tony Luck List of files: /linux-6.15/fs/pstore/Makefile

9d5438f4 - pstore: Add pmsg - user-space accessible pstore object

Sat, 17 Jan 2015 00:01:10 +0000

pstore: Add pmsg - user-space accessible pstore objectA secured user-space accessible pstore object. Writesto /dev/pmsg0 are appended to the buffer, on rebootthe persistent contents are available in/sys/fs/pstore/pmsg-ramoops-[ID].One possible use is syslogd, or other daemon, canwrite messages, then on reboot provides a means totriage user-space activities leading up to a panicas a companion to the pstore dmesg or console logs.Signed-off-by: Mark Salyzyn Acked-by: Kees Cook Signed-off-by: Tony Luck List of files: /linux-6.15/fs/pstore/Makefile

060287b8 - pstore: Add persistent function tracing

Tue, 10 Jul 2012 00:10:41 +0000

pstore: Add persistent function tracingWith this support kernel can save function call chain log into apersistent ram buffer that can be decoded and dumped after rebootthrough pstore filesystem. It can be used to determine what functionwas last called before a reset or panic.We store the log in a binary format and then decode it at read time.p.s.Mostly the code comes from trace_persistent.c driver found in theAndroid git tree, written by Colin Cross (according to sign-off history). I reworked the driver a little bit,and ported it to pstore.Signed-off-by: Anton Vorontsov Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/fs/pstore/Makefile

cddb8751 - staging: android: persistent_ram: Move to fs/pstore/ram_core.c

Thu, 17 May 2012 07:15:08 +0000

staging: android: persistent_ram: Move to fs/pstore/ram_core.cThis is a first step for adding ECC support for pstore RAM backend: wewill use the persistent_ram routines, kindly provided by Google.Basically, persistent_ram is a set of helper routines to deal with the[optionally] ECC-protected persistent ram regions.A bit of Makefile, Kconfig and header files adjustments were neededbecause of the move.Signed-off-by: Anton Vorontsov Acked-by: Kees Cook Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/fs/pstore/Makefile

1894a253 - ramoops: Move to fs/pstore/ram.c

Wed, 16 May 2012 12:43:08 +0000

ramoops: Move to fs/pstore/ram.cSince ramoops was converted to pstore, it has nothing to do with characterdevices nowadays. Instead, today it is just a RAM backend for pstore.The patch just moves things around. There are a few changes were neededbecause of the move:1. Kconfig and Makefiles fixups, of course.2. In pstore/ram.c we have to play a bit with MODULE_PARAM_PREFIX, this is needed to keep user experience the same as with ramoops driver (i.e. so that ramoops.foo kernel command line arguments would still work).Signed-off-by: Anton Vorontsov Acked-by: Marco Stornelli Acked-by: Kees Cook Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/fs/pstore/Makefile

ca01d6dd - pstore: new filesystem interface to platform persistent storage

Tue, 28 Dec 2010 22:25:21 +0000

pstore: new filesystem interface to platform persistent storageSome platforms have a small amount of non-volatile storage thatcan be used to store information useful to diagnose the cause ofa system crash. This is the generic part of a file system interfacethat presents information from the crash as a series of files in/dev/pstore. Once the information has been seen, the underlyingstorage is freed by deleting the files.Signed-off-by: Tony Luck List of files: /linux-6.15/fs/pstore/Makefile