qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH STABLE-0.12] block/vvfat.c: fix warnings with _FORTIFY_SOURCE
Date: Tue, 22 Jun 2010 10:15:29 +0200	[thread overview]
Message-ID: <m31vbzh49q.fsf@trasno.mitica> (raw)
In-Reply-To: <8565079cfd2bbfe3cba8c4f073d4c142937e3dee.1277191581.git.amit.shah@redhat.com> (Amit Shah's message of "Tue, 22 Jun 2010 12:56:26 +0530")

Amit Shah <amit.shah@redhat.com> wrote:
> From: Kirill A. Shutemov <kirill@shutemov.name>
>
> CC    block/vvfat.o
> cc1: warnings being treated as errors
> block/vvfat.c: In function 'commit_one_file':
> block/vvfat.c:2259: error: ignoring return value of 'ftruncate', declared with attribute warn_unused_result
> make: *** [block/vvfat.o] Error 1
>   CC    block/vvfat.o
> In file included from /usr/include/stdio.h:912,
>                  from ./qemu-common.h:19,
>                  from block/vvfat.c:27:
> In function 'snprintf',
>     inlined from 'init_directories' at block/vvfat.c:871,
>     inlined from 'vvfat_open' at block/vvfat.c:1068:
> /usr/include/bits/stdio2.h:65: error: call to __builtin___snprintf_chk will always overflow destination buffer
> make: *** [block/vvfat.o] Error 1
>
> Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> (cherry picked from commit 2dedf83ef0cc3463783d6b71bf1b25476f691f3a)
>
> Signed-off-by: Amit Shah <amit.shah@redhat.com>

Acked-by: Juan Quintela <quintela@redhat.com>

      reply	other threads:[~2010-06-22  8:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22  7:26 [Qemu-devel] [PATCH STABLE-0.12] block/vvfat.c: fix warnings with _FORTIFY_SOURCE Amit Shah
2010-06-22  8:15 ` Juan Quintela [this message]

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=m31vbzh49q.fsf@trasno.mitica \
    --to=quintela@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=amit.shah@redhat.com \
    --cc=kirill@shutemov.name \
    --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).