summaryrefslogtreecommitdiffstats
path: root/fs/pstore/pmsg.c
diff options
context:
space:
mode:
authorSebastian Andrzej Siewior <bigeasy@linutronix.de>2016-09-08 13:48:06 +0200
committerKees Cook <keescook@chromium.org>2016-09-08 15:00:47 -0700
commitd5a9bf0b38d2ac85c9a693c7fb851f74fd2a2494 (patch)
tree223697a08dc1c7209ed40545bb5561ca4c23c6dc /fs/pstore/pmsg.c
parent4407de74df18ed405cc5998990004c813ccfdbde (diff)
downloadlinux-d5a9bf0b38d2ac85c9a693c7fb851f74fd2a2494.tar.gz
linux-d5a9bf0b38d2ac85c9a693c7fb851f74fd2a2494.tar.bz2
linux-d5a9bf0b38d2ac85c9a693c7fb851f74fd2a2494.zip
pstore/core: drop cmpxchg based updates
I have here a FPGA behind PCIe which exports SRAM which I use for pstore. Now it seems that the FPGA no longer supports cmpxchg based updates and writes back 0xff…ff and returns the same. This leads to crash during crash rendering pstore useless. Since I doubt that there is much benefit from using cmpxchg() here, I am dropping this atomic access and use the spinlock based version. Cc: Anton Vorontsov <anton@enomsg.org> Cc: Colin Cross <ccross@android.com> Cc: Kees Cook <keescook@chromium.org> Cc: Tony Luck <tony.luck@intel.com> Cc: Rabin Vincent <rabinv@axis.com> Tested-by: Rabin Vincent <rabinv@axis.com> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Reviewed-by: Guenter Roeck <linux@roeck-us.net> [kees: remove "_locked" suffix since it's the only option now] Signed-off-by: Kees Cook <keescook@chromium.org> Cc: stable@vger.kernel.org
Diffstat (limited to 'fs/pstore/pmsg.c')
0 files changed, 0 insertions, 0 deletions