All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH]  stream fixes for migration
Date: Tue, 05 Apr 2005 02:18:10 +0100	[thread overview]
Message-ID: <4251E752.3070500@blueyonder.co.uk> (raw)
In-Reply-To: <s2516717.069@sinclair.provo.novell.com>

Charles Coffing wrote:
> I've attached a patch for libxutil/libxc.  This fixes one of the hangs I've seen during migrations.  It applies against 2.0 and 2.0-testing.
> 
> Changes:
>  * Encountering EOF or error when xfrd reads from stream could cause an infinite loop.
>  * Cleaned up the closing of streams.
>  * Fixed several memory leaks.

Is it possible for IOStreams to be used concurrently, or are they only
used in a single-threaded manner?

-- 
David Hopwood <david.nospam.hopwood@blueyonder.co.uk>

  reply	other threads:[~2005-04-05  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 22:10 [PATCH] stream fixes for migration Charles Coffing
2005-04-05  1:18 ` David Hopwood [this message]
2005-04-05  1:32   ` Adam Heath
2005-04-04  1:41     ` Mark Williamson
2005-04-05  1:57       ` David Hopwood
  -- strict thread matches above, loose matches on Subject: below --
2005-04-04 22:27 Ian Pratt

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=4251E752.3070500@blueyonder.co.uk \
    --to=david.nospam.hopwood@blueyonder.co.uk \
    --cc=xen-devel@lists.xensource.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.