summaryrefslogtreecommitdiff
path: root/shell-completion
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2014-12-30 20:57:53 +0100
committerLennart Poettering <lennart@poettering.net>2015-01-05 01:40:51 +0100
commitfa6ac76083b8ffc1309876459f54f9f0e2843731 (patch)
tree5169233d54825b07e63da5d11fbc3b4e248aa38b /shell-completion
parentf93bf4363395018ef48d744c4624158623afd693 (diff)
journald: process SIGBUS for the memory maps we set up
Even though we use fallocate() it appears that file systems like btrfs will trigger SIGBUS on certain low-disk-space situation. We should handle that, hence catch the signal, add it to a list of invalidated pages, and replace the page with an empty memory area. After each write check if SIGBUS was triggered, and consider the write invalid if it was. This should make journald a lot more robust with file systems where fallocate() is not reliable, for example all CoW file systems (btrfs...), where changing written data can fail with disk full errors. https://bugzilla.redhat.com/show_bug.cgi?id=1045810
Diffstat (limited to 'shell-completion')
0 files changed, 0 insertions, 0 deletions