Mailinglist Archive: opensuse-bugs (6165 mails)
| < Previous | Next > |
[Bug 618678] blkback thread hangs after unsuccessful xen domU start
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Mon, 5 Jul 2010 09:56:35 +0000
- Message-id: <20100705095635.203C024551D@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=618678
http://bugzilla.novell.com/show_bug.cgi?id=618678#c15
--- Comment #15 from Jan Beulich <jbeulich@xxxxxxxxxx> 2010-07-05 09:56:32 UTC
---
The semaphore is required to avoid races between user mode access through sysfs
(calling netback_uevent()) and teardown of a backend (see the email thread
surrounding
http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01570.html).
It does look like the locking I added was indeed too aggressive - I just wonder
how that got through all sorts of testing during the minimally 5 weeks that
this has been in place. Apparently the write lock ought to be acquired only
after calling kobject_uevent().
With that adjustment I hope we can get back to the problem originally reported
here...
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=618678#c15
--- Comment #15 from Jan Beulich <jbeulich@xxxxxxxxxx> 2010-07-05 09:56:32 UTC
---
The semaphore is required to avoid races between user mode access through sysfs
(calling netback_uevent()) and teardown of a backend (see the email thread
surrounding
http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01570.html).
It does look like the locking I added was indeed too aggressive - I just wonder
how that got through all sorts of testing during the minimally 5 weeks that
this has been in place. Apparently the write lock ought to be acquired only
after calling kobject_uevent().
With that adjustment I hope we can get back to the problem originally reported
here...
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |