All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Hajnoczi <stefanha@gmail.com>,
	zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: kwolf@redhat.com, lkurusa@redhat.com, mst@redhat.com,
	jan.kiszka@siemens.com, riku.voipio@iki.fi,
	luonengjun@huawei.com, qemu-devel@nongnu.org,
	peter.huangpeng@huawei.com, stefanha@redhat.com,
	Li Liu <john.liuli@huawei.com>,
	pbonzini@redhat.com, lcapitulino@redhat.com,
	alex.bennee@linaro.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v5 10/10] block/vvfat: fix setbuf stream parameter may be NULL
Date: Mon, 08 Sep 2014 14:57:21 +0400	[thread overview]
Message-ID: <540D8B91.1060805@msgid.tls.msk.ru> (raw)
In-Reply-To: <20140908083754.GC7638@stefanha-thinkpad.redhat.com>

08.09.2014 12:37, Stefan Hajnoczi wrote:
> On Mon, Aug 11, 2014 at 04:53:09PM +0800, zhanghailiang wrote:
>> From: Li Liu <john.liuli@huawei.com>
>>
>> fopen() may return NULL which will cause setbuf() segmentfault
[]
> This no longer exists:
> 
> commit 13b552c2f43298a42e26d7aec7b58a5c205b75a0
> Author: Michael Tokarev <mjt@tls.msk.ru>
> Date:   Wed Aug 20 19:02:38 2014 +0400
> 
>     block/vvfat.c: remove debugging code to reinit stderr if NULL

The second patch is a result of discussion emerged after first patch,
consider the commit to be a follow-up for the initial patch :)

Thanks,

/mjt

      reply	other threads:[~2014-09-08 10:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11  8:52 [Qemu-devel] [PATCH v5 00/10] fix three bugs about use-after-free and several api abuse zhanghailiang
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 01/10] l2cap: fix access freed memory zhanghailiang
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 02/10] monitor: " zhanghailiang
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 03/10] virtio-blk: fix reference a pointer which might be freed zhanghailiang
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 04/10] ivshmem: check the value returned by fstat() zhanghailiang
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 05/10] util/path: Use the GLib memory allocation routines zhanghailiang
2014-08-11  9:32   ` Alex Bennée
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 06/10] slirp/misc: Use g_malloc() instead of malloc() zhanghailiang
2014-08-11  9:33   ` Alex Bennée
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 07/10] linux-user: check return value " zhanghailiang
2014-08-12  7:34   ` Riku Voipio
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 08/10] tests/bios-tables-test: check the value returned by fopen() zhanghailiang
2014-08-11  9:33   ` Alex Bennée
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 09/10] tcg: check return value of fopen() zhanghailiang
2014-08-11  9:34   ` Alex Bennée
2014-08-11  8:53 ` [Qemu-devel] [PATCH v5 10/10] block/vvfat: fix setbuf stream parameter may be NULL zhanghailiang
2014-09-08  8:37   ` Stefan Hajnoczi
2014-09-08 10:57     ` Michael Tokarev [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=540D8B91.1060805@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=alex.bennee@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=john.liuli@huawei.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=lkurusa@redhat.com \
    --cc=luonengjun@huawei.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=rth@twiddle.net \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=zhang.zhanghailiang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.