Displaying 11 results from an estimated 11 matches for "bitmap_endwrit".
Did you mean:
bitmap_endwrite
2014 Jun 27
2
virt_blk BUG: sleeping function called from invalid context
...c(): 1, irqs_disabled(): 1, pid: 0, name: swapper/1
2 locks held by swapper/1/0:
#0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>]
virtblk_done+0x42/0xe0 [virtio_blk]
#1: (&(&bitmap->counts.lock)->rlock){-.....}, at:
[<ffffffff81633718>] bitmap_endwrite+0x68/0x240
irq event stamp: 33518
hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230
hardirqs last disabled at (33516): [<ffffffff818122ed>]
common_interrupt+0x6d/0x72
softirqs last enabled at (33518): [<ffffffff810a1272>]
_local_bh_enable+0x22/0...
2014 Jun 27
2
virt_blk BUG: sleeping function called from invalid context
...c(): 1, irqs_disabled(): 1, pid: 0, name: swapper/1
2 locks held by swapper/1/0:
#0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>]
virtblk_done+0x42/0xe0 [virtio_blk]
#1: (&(&bitmap->counts.lock)->rlock){-.....}, at:
[<ffffffff81633718>] bitmap_endwrite+0x68/0x240
irq event stamp: 33518
hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230
hardirqs last disabled at (33516): [<ffffffff818122ed>]
common_interrupt+0x6d/0x72
softirqs last enabled at (33518): [<ffffffff810a1272>]
_local_bh_enable+0x22/0...
2014 Jun 29
0
virt_blk BUG: sleeping function called from invalid context
...1, pid: 0, name: swapper/1
> 2 locks held by swapper/1/0:
> #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>]
> virtblk_done+0x42/0xe0 [virtio_blk]
> #1: (&(&bitmap->counts.lock)->rlock){-.....}, at:
> [<ffffffff81633718>] bitmap_endwrite+0x68/0x240
> irq event stamp: 33518
> hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230
> hardirqs last disabled at (33516): [<ffffffff818122ed>]
> common_interrupt+0x6d/0x72
> softirqs last enabled at (33518): [<ffffffff810a1272>...
2014 Jul 01
3
[PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
...c(): 1, irqs_disabled(): 1, pid: 0, name: swapper/1
2 locks held by swapper/1/0:
#0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>] virtblk_done+0x42/0xe0 [virtio_blk]
#1: (&(&bitmap->counts.lock)->rlock){-.....}, at: [<ffffffff81633718>] bitmap_endwrite+0x68/0x240
irq event stamp: 33518
hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230
hardirqs last disabled at (33516): [<ffffffff818122ed>] common_interrupt+0x6d/0x72
softirqs last enabled at (33518): [<ffffffff810a1272>] _local_bh_enable+0x22/0...
2014 Jul 01
3
[PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
...c(): 1, irqs_disabled(): 1, pid: 0, name: swapper/1
2 locks held by swapper/1/0:
#0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>] virtblk_done+0x42/0xe0 [virtio_blk]
#1: (&(&bitmap->counts.lock)->rlock){-.....}, at: [<ffffffff81633718>] bitmap_endwrite+0x68/0x240
irq event stamp: 33518
hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230
hardirqs last disabled at (33516): [<ffffffff818122ed>] common_interrupt+0x6d/0x72
softirqs last enabled at (33518): [<ffffffff810a1272>] _local_bh_enable+0x22/0...
2014 Jun 29
2
virt_blk BUG: sleeping function called from invalid context
...called
>> from irq context. The problem is that the MD bio end_io handler is calling
>> a sleeping function. Not sure if that's a bug in MD though given the
>> kernfs symbols in the all trace and the recent churn in that area.
>
> My understanding is this:
>
> bitmap_endwrite -> calls sysfs_notify_dirent_safe under spinlock
> -> calls kernfs_notify which takes a mutex.
>
> So I am guessing it is this commit:
>
> commit d911d98748018f7c8facc035ba39c30f5cce6f9c
> Author: Tejun Heo <tj at kernel.org>
> Date: Wed Apr 9 11:07:31 2014 -0...
2014 Jun 29
2
virt_blk BUG: sleeping function called from invalid context
...called
>> from irq context. The problem is that the MD bio end_io handler is calling
>> a sleeping function. Not sure if that's a bug in MD though given the
>> kernfs symbols in the all trace and the recent churn in that area.
>
> My understanding is this:
>
> bitmap_endwrite -> calls sysfs_notify_dirent_safe under spinlock
> -> calls kernfs_notify which takes a mutex.
>
> So I am guessing it is this commit:
>
> commit d911d98748018f7c8facc035ba39c30f5cce6f9c
> Author: Tejun Heo <tj at kernel.org>
> Date: Wed Apr 9 11:07:31 2014 -0...
2014 Jul 01
0
[PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
...sabled(): 1, pid: 0, name: swapper/1
> 2 locks held by swapper/1/0:
> #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>] virtblk_done+0x42/0xe0 [virtio_blk]
> #1: (&(&bitmap->counts.lock)->rlock){-.....}, at: [<ffffffff81633718>] bitmap_endwrite+0x68/0x240
> irq event stamp: 33518
> hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230
> hardirqs last disabled at (33516): [<ffffffff818122ed>] common_interrupt+0x6d/0x72
> softirqs last enabled at (33518): [<ffffffff810a1272>] _lo...
2014 Jun 29
2
virt_blk BUG: sleeping function called from invalid context
On Sun, Jun 29, 2014 at 11:26:37AM +0300, Michael S. Tsirkin wrote:
> On Fri, Jun 27, 2014 at 07:57:38AM -0400, Josh Boyer wrote:
> > Hi All,
> >
> > We've had a report[1] of the virt_blk driver causing a lot of spew
> > because it's calling a sleeping function from an invalid context. The
> > backtrace is below. This is with kernel
2014 Jun 29
2
virt_blk BUG: sleeping function called from invalid context
On Sun, Jun 29, 2014 at 11:26:37AM +0300, Michael S. Tsirkin wrote:
> On Fri, Jun 27, 2014 at 07:57:38AM -0400, Josh Boyer wrote:
> > Hi All,
> >
> > We've had a report[1] of the virt_blk driver causing a lot of spew
> > because it's calling a sleeping function from an invalid context. The
> > backtrace is below. This is with kernel
2014 Jun 29
0
virt_blk BUG: sleeping function called from invalid context
...blk_mq_end_io is supposed to be called
> from irq context. The problem is that the MD bio end_io handler is calling
> a sleeping function. Not sure if that's a bug in MD though given the
> kernfs symbols in the all trace and the recent churn in that area.
My understanding is this:
bitmap_endwrite -> calls sysfs_notify_dirent_safe under spinlock
-> calls kernfs_notify which takes a mutex.
So I am guessing it is this commit:
commit d911d98748018f7c8facc035ba39c30f5cce6f9c
Author: Tejun Heo <tj at kernel.org>
Date: Wed Apr 9 11:07:31 2014 -0400
kernfs: make kernfs_notify...