diff options
| author | Omar Sandoval <osandov@fb.com> | 2016-05-11 15:16:37 -0700 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2016-05-12 16:55:50 -0400 |
| commit | 2c4cb04300fa160e9d78335c74184c4e66a56437 (patch) | |
| tree | ff36e8066fe5092e23cc2519adfd976eb54bc0b8 /fs/ecryptfs | |
| parent | a00839395103d5e2d132a6c4a9680256580ed3d1 (diff) | |
| download | linux-2c4cb04300fa160e9d78335c74184c4e66a56437.tar.gz linux-2c4cb04300fa160e9d78335c74184c4e66a56437.tar.bz2 linux-2c4cb04300fa160e9d78335c74184c4e66a56437.zip | |
coredump: only charge written data against RLIMIT_CORE
Commit 9b56d54380ad ("dump_skip(): dump_seek() replacement taking
coredump_params") introduced a regression with regard to RLIMIT_CORE.
Previously, when a core dump was sparse, only the data that was actually
written out would count against the limit. Now, the sparse ranges are
also included, which leads to truncated core dumps when the actual disk
usage is still well below the limit. Restore the old behavior by only
counting what gets emitted and ignoring what gets skipped.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/ecryptfs')
0 files changed, 0 insertions, 0 deletions