From: Eric Blake <eblake@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
Qiao Nuohan <qiaonuohan@cn.fujitsu.com>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org,
lcapitulino@redhat.com, anderson@redhat.com,
kumagai-atsushi@mxc.nes.nec.co.jp, akong@redhat.com,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v6 09/11] dump: Add API to write dump pages
Date: Tue, 07 Jan 2014 16:12:56 -0700 [thread overview]
Message-ID: <52CC89F8.4090203@redhat.com> (raw)
In-Reply-To: <52CC81B9.1080609@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
On 01/07/2014 03:37 PM, Laszlo Ersek wrote:
> comments below
>
> On 01/05/14 08:27, Qiao Nuohan wrote:
>> functions are used to write page to vmcore. vmcore is written page by page.
>> page desc is used to store the information of a page, including a page's size,
>> offset, compression format, etc.
>>
>> + uint64_t pfn_start, pfn_end, pfn;
>> + unsigned char buf[s->page_size];
>
> Whoa, a VLA! :) I believe it's *very* non-idiomatic in the qemu source.
> Please consider allocating it dynamically. (Of course others might point
> out that I'm wrong.)
Worse, a stack allocation greater than the size of a stack frame. Any
time you have a function taking more than a page size of local storage,
you risk nasty behavior on some platforms (Windows in particular is
notorious for giving you only a single guard page, and if you overflow
the stack by more than the guard page, your program is unceremoniously
terminated with no message, compared to the usual desirable behavior of
getting a SIGSEGV that your program can at least react to in order to
diagnose that you had a stack overflow).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-01-07 23:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 7:27 [Qemu-devel] [PATCH v6 00/11] Make 'dump-guest-memory' dump in kdump-compressed format Qiao Nuohan
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 01/11] dump: Add argument to write_elfxx_notes Qiao Nuohan
2014-01-06 17:03 ` Laszlo Ersek
2014-01-07 6:00 ` Qiao Nuohan
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 02/11] dump: Add API to write header of flatten format Qiao Nuohan
2014-01-06 17:15 ` Laszlo Ersek
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 03/11] dump: Add API to write vmcore Qiao Nuohan
2014-01-06 18:12 ` Laszlo Ersek
2014-01-07 6:15 ` Qiao Nuohan
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 04/11] dump: Add API to write elf notes to buffer Qiao Nuohan
2014-01-06 18:46 ` Laszlo Ersek
2014-01-07 6:17 ` Qiao Nuohan
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 05/11] dump: add support for lzo/snappy Qiao Nuohan
2014-01-06 19:25 ` Laszlo Ersek
2014-01-07 6:25 ` Qiao Nuohan
2014-01-07 7:24 ` Laszlo Ersek
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 06/11] dump: add API to write dump header Qiao Nuohan
2014-01-07 11:38 ` Laszlo Ersek
2014-01-07 11:49 ` Andreas Färber
2014-01-13 10:03 ` Qiao Nuohan
2014-01-13 10:39 ` Laszlo Ersek
2014-01-14 2:07 ` Qiao Nuohan
2014-01-14 2:29 ` Laszlo Ersek
2014-01-14 2:42 ` Qiao Nuohan
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 07/11] dump: Add API to write dump_bitmap Qiao Nuohan
2014-01-07 14:49 ` Laszlo Ersek
2014-01-07 21:41 ` Laszlo Ersek
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 08/11] dump: Add APIs to operate DataCache Qiao Nuohan
2014-01-07 15:22 ` Laszlo Ersek
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 09/11] dump: Add API to write dump pages Qiao Nuohan
2014-01-07 22:37 ` Laszlo Ersek
2014-01-07 23:12 ` Eric Blake [this message]
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 10/11] dump: Make kdump-compressed format available for 'dump-guest-memory' Qiao Nuohan
2014-01-09 15:46 ` Laszlo Ersek
2014-01-05 7:27 ` [Qemu-devel] [PATCH v6 11/11] Add 'query-dump-guest-memory-capability' command Qiao Nuohan
2014-01-09 16:34 ` Laszlo Ersek
2014-01-07 6:32 ` [Qemu-devel] [PATCH v6 00/11] Make 'dump-guest-memory' dump in kdump-compressed format Qiao Nuohan
2014-01-07 7:27 ` Laszlo Ersek
2014-01-07 7:30 ` Qiao Nuohan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CC89F8.4090203@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=akong@redhat.com \
--cc=anderson@redhat.com \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=lcapitulino@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qiaonuohan@cn.fujitsu.com \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).