All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murillo Bernardes <mfb@br.ibm.com>
To: xen-devel@lists.xensource.com
Subject: Errors on net and block drivers - my summary
Date: Tue, 22 Nov 2005 18:47:32 -0200	[thread overview]
Message-ID: <200511221847.32644.mfb@br.ibm.com> (raw)

Hi

Here is some errors I collected last days on net and block drivers.

1. Frontend directories are not been removed from store on 
{network,block}-detach. Makes xm {network,block}-list show closed devices.

2. Attach a block device after detach that does not work and does not report 
failure - Bug #420.

3. Frontend devices are not been unregistered on {network,block}-detach. 
Causes Bug #420.

4. If a domain die/crash/whatever all backend devices still on dom0.

5. xm {network,block}-{attach,dettach} does not check if operation was 
sucessfull on frontend. (ie. attach more than 3 vif fails, but xm 
network-attach does not report failure)

6. Attach more than 3 vif makes domU kernel OOPS. (probably 
drivers/xen/xenbus/xenbus_probe.c:307-308)

Time to go. Tomorrow I will work on this errors again, and probably file bug 
reports for all of them.

Thanks

-- 
Murillo Fernandes Bernardes
IBM Linux Technology Center

                 reply	other threads:[~2005-11-22 20:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200511221847.32644.mfb@br.ibm.com \
    --to=mfb@br.ibm.com \
    --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.