From: "Kirill A. Shutemov" <k.shutemov@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [BUG] [PATCH] qemu -snapshot
Date: Thu, 8 Feb 2007 11:00:50 +0300 [thread overview]
Message-ID: <20070208080050.GA10997@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 107 bytes --]
Buffer for second argument of realpath should be size PATH_MAX.
Patch by Sergey Vlasov in the attachment.
[-- Attachment #1.2: qemu-0.9.0-alt-realpath.patch --]
[-- Type: text/plain, Size: 441 bytes --]
--- qemu-0.9.0/block.c.alt-realpath 2007-02-06 22:06:26 +0300
+++ qemu-0.9.0/block.c 2007-02-06 22:16:31 +0300
@@ -326,8 +326,8 @@ int bdrv_open2(BlockDriverState *bs, con
BlockDriver *drv)
{
int ret, open_flags;
- char tmp_filename[1024];
- char backing_filename[1024];
+ char tmp_filename[PATH_MAX];
+ char backing_filename[PATH_MAX];
bs->read_only = 0;
bs->is_temporary = 0;
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2007-02-08 9:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070208080050.GA10997@localhost.localdomain \
--to=k.shutemov@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).