All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Andreas Olsowski <andreas.olsowski@leuphana.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: hanging tapdisk2 processes and improper udev rules
Date: Fri, 22 Jul 2011 15:32:50 +0100	[thread overview]
Message-ID: <1311345170.12772.81.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <4E2988FB.40904@leuphana.de>

On Fri, 2011-07-22 at 15:28 +0100, Andreas Olsowski wrote:
> >> My expertise with C is barely existant, but i took a look at
> >> tools/libxl/libxl_device.c
> >>
> >> and changed your
> >> libxl__device_destroy_tapdisk(gc, be_path);
> >> into
> >> libxl__device_destroy_tapdisk(&gc, be_path);
> >>
> >> as i have seen some&gc on other lines of code.
> >
> > That looks right. I think this is just a difference between current
> > xen-unstable and xen-4.1 (due to 23045:c426a7140c99 FWIW).
> What do you mean looks right, the compilation errors or my 
> shot-in-the-dark adjustment?

Your fix looked sensible.

> 
> > Uh. That really shouldn't happen :-/ In fact baring a bug in the host OS
> > itself I'm not sure how ps can ever get into that state...
> I had this happen before on two occasions (one of them using xm to 
> create a guest, whereas xl worked fine) and Sébastien Riccio wrote in 
> this thread, that he encountered it too.
> If this one returns during "normal operation", ill write some more.
> 
> > It's possible that it relies on something in xen-unstable that I'm not
> > aware of. Would it be possible for you to try and repro this issue with
> > xen-unstable.hg and this patch?
> Yes, i can and will do that.
> Probably later this evening (4PM here now), but definitely this weekend.
> I will reply to this thread with the results.

Thanks.

Ian.

  reply	other threads:[~2011-07-22 14:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22  9:18 hanging tapdisk2 processes and improper udev rules Andreas Olsowski
2011-07-22  9:28 ` Ian Campbell
2011-07-22 11:36   ` Andreas Olsowski
2011-07-22 14:07     ` Ian Campbell
2011-07-22 14:28       ` Andreas Olsowski
2011-07-22 14:32         ` Ian Campbell [this message]
2011-07-25  8:55           ` Andreas Olsowski
2011-08-11 13:32           ` Andreas Olsowski
2011-07-22  9:31 ` Daniel Stodden
2011-07-22  9:32   ` Daniel Stodden
2011-07-22  9:34   ` Sébastien RICCIO
2011-07-22  9:50     ` Daniel Stodden
2011-07-22 10:01       ` Sébastien RICCIO
2011-07-22 18:55         ` hanging tapdisk2 processes and multipathing Daniel Stodden

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=1311345170.12772.81.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@eu.citrix.com \
    --cc=andreas.olsowski@leuphana.de \
    --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.