summaryrefslogtreecommitdiff
path: root/qemu-io.c
diff options
context:
space:
mode:
authorLaszlo Ersek <lersek@redhat.com>2013-08-06 12:37:08 +0200
committerLuiz Capitulino <lcapitulino@redhat.com>2013-08-08 11:01:45 -0400
commit2cac260768b9d4253737417ea7501cf2950e257f (patch)
tree2599bc433898e4172076b62db91e8acc49849e9d /qemu-io.c
parent6fdf98f281f85ae6e2883bed2f691bcfe33b1f9f (diff)
downloadqemu-2cac260768b9d4253737417ea7501cf2950e257f.tar.gz
qemu-2cac260768b9d4253737417ea7501cf2950e257f.tar.bz2
qemu-2cac260768b9d4253737417ea7501cf2950e257f.zip
dump: clamp guest-provided mapping lengths to ramblock sizes
Even a trusted & clean-state guest can map more memory than what it was given. Since the vmcore contains RAMBlocks, mapping sizes should be clamped to RAMBlock sizes. Otherwise such oversized mappings can exceed the entire file size, and ELF parsers might refuse even the valid portion of the PT_LOAD entry. Related RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=981582 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Diffstat (limited to 'qemu-io.c')
0 files changed, 0 insertions, 0 deletions