From: Hitoshi Mitake <mitake.hitoshi@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, mitake.hitoshi@gmail.com,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/4] qemu-io: initialize progname with error_set_progname()
Date: Mon, 02 Feb 2015 23:04:52 +0900 [thread overview]
Message-ID: <87y4og76kb.wl%mitake.hitoshi@gmail.com> (raw)
In-Reply-To: <20150202113600.GA9478@noname.redhat.com>
At Mon, 2 Feb 2015 12:36:00 +0100,
Kevin Wolf wrote:
>
> Am 02.02.2015 um 10:51 hat Hitoshi Mitake geschrieben:
> > At Thu, 22 Jan 2015 18:08:11 +0900,
> > Hitoshi Mitake wrote:
> > >
> > > Calling error_get_progname() in the context of qemu-io can cause
> > > segmentation fault because qemu-io doesn't initialize its progname
> > > with error_set_progname(). This patch adds the initialization.
> > >
> > > Currently, the missing call of error_set_progname() doesn't cause any
> > > problems because qemu-io doesn't use error_get_progname(). This patch
> > > is a proactive action.
> > >
> > > Cc: Kevin Wolf <kwolf@redhat.com>
> > > Cc: Stefan Hajnoczi <stefanha@redhat.com>
> > > Cc: Markus Armbruster <armbru@redhat.com>
> > > Signed-off-by: Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>
> > > ---
> > > qemu-io.c | 1 +
> > > 1 file changed, 1 insertion(+)
> >
> > Hi Kevin, Stefan, could you pick this patch? sheepdog driver has a
> > pending patch [1] which depends on it. I believe at least qemu-io
> > should call error_set_progname() because block drivers can use the
> > qemu-error infrastructure.
>
> So are you planning to get the individual patches merged on their own
> instead of the whole series as one?
I thought this patchset can be proactive fix. So I'm separating the
patch for sheepdog driver from this one.
>
> > [1] https://github.com/sheepdog/qemu/commit/a95c35e606a2a189e7dbaf645277c5c306b01e4b
>
> That patch looks wrong. Nobody guarantees that qemu-io is really called
> qemu-io. The user can name their binaries as they want and create
> symlinks with any name, and indeed names for qemu-img used by some
> distributions include 'qemu-img-kvm' and 'kvm-img'. You need to find a
> different way than checking binary file names.
I couldn't consider about the case, thanks for pointing! I'll seek
other method for distinguishing binary files.
Thanks,
Hitoshi
>
> Kevin
next prev parent reply other threads:[~2015-02-02 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 9:08 [Qemu-devel] [PATCH v2 0/4] initialize progname with error_set_progname() Hitoshi Mitake
2015-01-22 9:08 ` [Qemu-devel] [PATCH v2 1/4] qemu-io: " Hitoshi Mitake
2015-02-02 9:51 ` Hitoshi Mitake
2015-02-02 11:36 ` Kevin Wolf
2015-02-02 14:04 ` Hitoshi Mitake [this message]
2015-01-22 9:08 ` [Qemu-devel] [PATCH v2 2/4] qemu-nbd: " Hitoshi Mitake
2015-01-22 9:08 ` [Qemu-devel] [PATCH v2 3/4] qga: " Hitoshi Mitake
2015-01-22 9:08 ` [Qemu-devel] [PATCH v2 4/4] linux-user: " Hitoshi Mitake
2015-01-22 10:07 ` Peter Maydell
2015-02-02 9:47 ` Hitoshi Mitake
2015-01-22 9:47 ` [Qemu-devel] [PATCH v2 0/4] " Markus Armbruster
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=87y4og76kb.wl%mitake.hitoshi@gmail.com \
--to=mitake.hitoshi@gmail.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.