summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorDave Kleikamp <dave.kleikamp@oracle.com>2017-01-11 13:25:00 -0600
committerAl Viro <viro@zeniv.linux.org.uk>2017-01-14 19:32:40 -0500
commit4d22c75d4c7b5c5f4bd31054f09103ee490878fd (patch)
treea58ff1b3bb440af13026891f6ccb38d36fffcb4c /include
parenta12f1ae61c489076a9aeb90bddca7722bf330df3 (diff)
downloadlinux-4d22c75d4c7b5c5f4bd31054f09103ee490878fd.tar.bz2
coredump: Ensure proper size of sparse core files
If the last section of a core file ends with an unmapped or zero page, the size of the file does not correspond with the last dump_skip() call. gdb complains that the file is truncated and can be confusing to users. After all of the vma sections are written, make sure that the file size is no smaller than the current file position. This problem can be demonstrated with gdb's bigcore testcase on the sparc architecture. Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com> Cc: Alexander Viro <viro@zeniv.linux.org.uk> Cc: linux-fsdevel@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'include')
-rw-r--r--include/linux/coredump.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/coredump.h b/include/linux/coredump.h
index d016a121a8c4..28ffa94aed6b 100644
--- a/include/linux/coredump.h
+++ b/include/linux/coredump.h
@@ -14,6 +14,7 @@ struct coredump_params;
extern int dump_skip(struct coredump_params *cprm, size_t nr);
extern int dump_emit(struct coredump_params *cprm, const void *addr, int nr);
extern int dump_align(struct coredump_params *cprm, int align);
+extern void dump_truncate(struct coredump_params *cprm);
#ifdef CONFIG_COREDUMP
extern void do_coredump(const siginfo_t *siginfo);
#else