13 Feb, 2013

1 commit

• fb0af3f2b   pstore: Create a convenient mount point for pstore ... Browse Code »

  Using /dev/pstore as a mount point for the pstore filesystem is slightly
  awkward. We don't normally mount filesystems in /dev/ and the /dev/pstore
  file isn't created automatically by anything. While this method will
  still work, we can create a persistent mount point in sysfs. This will
  put pstore on par with things like cgroups and efivarfs.

  Signed-off-by: Josh Boyer
  Acked-by: Kees Cook
  Signed-off-by: Tony Luck

  Josh Boyer

  2013-02-13 05:07:22 +0800  

23 Jul, 2011

1 commit

• dee28e72b   pstore: Allow the user to explicitly choose a backend ... Browse Code »

  pstore only allows one backend to be registered at present, but the
  system may provide several. Add a parameter to allow the user to choose
  which backend will be used rather than just relying on load order.

  Signed-off-by: Matthew Garrett
  Signed-off-by: Tony Luck

  Matthew Garrett

  2011-07-23 07:14:39 +0800  

22 Mar, 2011

1 commit

• 366f7e7a7   pstore: use mount option instead sysfs to tweak kmsg_bytes ... Browse Code »

  /sys/fs is a somewhat strange way to tweak what could more
  obviously be tuned with a mount option.

  Suggested-by: Christoph Hellwig
  Signed-off-by: Tony Luck
  Signed-off-by: Linus Torvalds

  Luck, Tony

  2011-03-22 04:50:05 +0800  

29 Dec, 2010

1 commit

• ca01d6dd2   pstore: new filesystem interface to platform persistent storage ... Browse Code »

  Some platforms have a small amount of non-volatile storage that
  can be used to store information useful to diagnose the cause of
  a system crash. This is the generic part of a file system interface
  that presents information from the crash as a series of files in
  /dev/pstore. Once the information has been seen, the underlying
  storage is freed by deleting the files.

  Signed-off-by: Tony Luck

  Tony Luck

  2010-12-29 06:25:21 +0800