All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Matt Wilson <msw@amazon.com>
Cc: Joe Jin <joe.jin@oracle.com>, xen-devel@lists.xen.org
Subject: Re: [RFC] [PATCH] xen/blkback: add locking in statistics sysfs show functions
Date: Thu, 26 Apr 2012 22:24:56 -0400	[thread overview]
Message-ID: <20120427022456.GA26931@phenom.dumpdata.com> (raw)
In-Reply-To: <1334949673-25632-2-git-send-email-msw@amazon.com>

On Fri, Apr 20, 2012 at 07:21:13PM +0000, Matt Wilson wrote:
> This is a port of a patch in the XenoLinux 2.6.18 tree:
> http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/rev/f47c07325a56
> 
> Fix blkback sysfs race

So with this patch I keep on getting this:

[  128.274290] switch: port 2(vif1.0) entered disabled state
[  128.855442] BUG: sleeping function called from invalid context at /home/konrad/ssd/linux/kernel/mutex.c:85
[  128.855628] in_atomic(): 1, irqs_disabled(): 0, pid: 46, name: xenwatch
[  128.855757] Pid: 46, comm: xenwatch Tainted: G           O 3.4.0-rc4upstream-00103-g7e4325c-dirty #1
[  128.855917] Call Trace:
[  128.856062]  [<ffffffff810983ea>] __might_sleep+0xda/0x100
[  128.856215]  [<ffffffff815a9267>] mutex_lock+0x27/0x50
[  128.856351]  [<ffffffff811b3039>] sysfs_get_dirent+0x29/0x80
[  128.856495]  [<ffffffff811b4d7b>] sysfs_remove_group+0x2b/0x100
[  128.856626]  [<ffffffff81393a20>] xenvbd_sysfs_delif+0x20/0x50
[  128.856756]  [<ffffffff81394518>] xen_blkbk_remove+0xe8/0xf0
[  128.856895]  [<ffffffff8131c768>] xenbus_dev_remove+0x38/0x70
[  128.857041]  [<ffffffff81381601>] __device_release_driver+0x61/0xc0
[  128.857177]  [<ffffffff81381778>] device_release_driver+0x28/0x40
[  128.857323]  [<ffffffff81380896>] bus_remove_device+0x106/0x140
[  128.857459]  [<ffffffff8137e868>] device_del+0x118/0x1c0
[  128.857580]  [<ffffffff8137e921>] device_unregister+0x11/0x20
[  128.857712]  [<ffffffff8139376a>] frontend_changed+0xba/0x350
[  128.857851]  [<ffffffff810337f9>] ? xen_irq_enable_direct_reloc+0x4/0x4
[  128.857982]  [<ffffffff8109928d>] ? finish_task_switch+0x4d/0x100
[  128.858106]  [<ffffffff8131ca18>] xenbus_otherend_changed+0xa8/0xb0
[  128.858236]  [<ffffffff815ab629>] ? _raw_spin_unlock_irqrestore+0x19/0x30
[  128.858368]  [<ffffffff8131cc2b>] frontend_changed+0xb/0x10
[  128.858522]  [<ffffffff8131ad3b>] xenwatch_thread+0xcb/0x190
[  128.858655]  [<ffffffff8108ec40>] ? wake_up_bit+0x40/0x40
[  128.858801]  [<ffffffff8131ac70>] ? xenbus_thread+0x320/0x320
[  128.858965]  [<ffffffff8108e716>] kthread+0x96/0xa0
[  128.859097]  [<ffffffff815b3564>] kernel_thread_helper+0x4/0x10
[  128.859235]  [<ffffffff815abb78>] ? retint_restore_args+0x5/0x6
[  128.859371]  [<ffffffff815b3560>] ? gs_change+0x13/0x13
[  128.859542] BUG: scheduling while atomic: xenwatch/46/0x00000002

whenever a guest is powered off.

  parent reply	other threads:[~2012-04-27  2:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20 19:21 [RFC] [PATCH] add locking in statistics sysfs show functions Matt Wilson
2012-04-20 19:21 ` [RFC] [PATCH] xen/blkback: " Matt Wilson
2012-04-26 20:51   ` Konrad Rzeszutek Wilk
2012-04-27  2:24   ` Konrad Rzeszutek Wilk [this message]
2012-04-27 16:30     ` Matt Wilson

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=20120427022456.GA26931@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=joe.jin@oracle.com \
    --cc=msw@amazon.com \
    --cc=xen-devel@lists.xen.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 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.