Revision 4d22c75d4c7b5c5f4bd31054f09103ee490878fd authored by Dave Kleikamp on 11 January 2017, 19:25:00 UTC, committed by Al Viro on 15 January 2017, 00:32:40 UTC
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>
1 parent a12f1ae
| File | Mode | Size |
|---|---|---|
| .gitignore | -rw-r--r-- | 44 bytes |
| Kconfig | -rw-r--r-- | 2.6 KB |
| Makefile | -rw-r--r-- | 3.7 KB |
| system_certificates.S | -rw-r--r-- | 917 bytes |
| system_keyring.c | -rw-r--r-- | 6.8 KB |
Computing file changes ...
