From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block/nfs: fix potential segfault on early callback
Date: Wed, 11 Jun 2014 13:46:32 +0200 [thread overview]
Message-ID: <20140611114632.GI6673@stefanha-thinkpad.str.redhat.com> (raw)
In-Reply-To: <1402386167-8091-1-git-send-email-pl@kamp.de>
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
On Tue, Jun 10, 2014 at 09:42:47AM +0200, Peter Lieven wrote:
> it will happen in the future that the callback of a libnfs call
> directly invokes the callback. In this case we end up in a segfault
> because the NFSRPC is gone when we the BH is scheduled.
>
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> block/nfs.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-06-11 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 7:42 [Qemu-devel] [PATCH] block/nfs: fix potential segfault on early callback Peter Lieven
2014-06-11 11:46 ` Stefan Hajnoczi [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=20140611114632.GI6673@stefanha-thinkpad.str.redhat.com \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--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).