Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1327212 > unrolled thread

Re: [lkp] [mm] 63c6a211b0: BUG: sleeping function called from invalid context at mm/memory.c:1207

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [lkp] [mm] 63c6a211b0: BUG: sleeping function called from  invalid context at mm/memory.c:1207 Andrew Morton <akpm@linux-foundation.org> - 2016-02-04 22:40 +0100
    Re: [LKP] [lkp] [mm] 63c6a211b0: BUG: sleeping function called from invalid context at mm/memory.c:1207 "Huang\, Ying" <ying.huang@intel.com> - 2016-02-05 03:00 +0100

#1327212 — Re: [lkp] [mm] 63c6a211b0: BUG: sleeping function called from invalid context at mm/memory.c:1207

On Thu, 04 Feb 2016 08:46:03 +0800 kernel test robot <ying.huang@linux.intel.com> wrote:

> FYI, we noticed the below changes on
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 63c6a211b0eb5b1c86ffdd9d89639fb7f1b70fca ("mm: workingset: per-cgroup cache thrash detection")
> 
> 
> [    8.134495]   No soundcards found.
> [    8.137598] debug: unmapping init [mem 0xffffffff81cdc000-0xffffffff81d99fff]
> [    8.137598] debug: unmapping init [mem 0xffffffff81cdc000-0xffffffff81d99fff]
> [    8.155388] BUG: sleeping function called from invalid context at mm/memory.c:1207
> [    8.155388] BUG: sleeping function called from invalid context at mm/memory.c:1207
> [    8.158212] in_atomic(): 0, irqs_disabled(): 0, pid: 79, name: mount
> [    8.158212] in_atomic(): 0, irqs_disabled(): 0, pid: 79, name: mount
> [    8.160436] 1 lock held by mount/79:
> [    8.160436] 1 lock held by mount/79:
> [    8.161488]  #0: 
> [    8.161488]  #0:  ( (rcu_read_lockrcu_read_lock){......}){......}, at: , at: [<ffffffff810e4cc9>] rcu_lock_acquire+0x0/0x20
> [<ffffffff810e4cc9>] rcu_lock_acquire+0x0/0x20
> [    8.164136] Preemption disabled at:
> [    8.164136] Preemption disabled at:[<ffffffff8106a358>] vprintk_default+0x18/0x1a
> [<ffffffff8106a358>] vprintk_default+0x18/0x1a

I'm not sure why this is pointing at vprintk_default...

mm-workingset-per-cgroup-cache-thrash-detection.patch does have a bug
which could cause this.  It's fixed by
mm-workingset-per-cgroup-cache-thrash-detection-fix.patch.  Was the
-fix patch applied during this testing?

[toc] | [next] | [standalone]

#1327396 — Re: [LKP] [lkp] [mm] 63c6a211b0: BUG: sleeping function called from invalid context at mm/memory.c:1207

Andrew Morton <akpm@linux-foundation.org> writes:

> On Thu, 04 Feb 2016 08:46:03 +0800 kernel test robot <ying.huang@linux.intel.com> wrote:
>
>> FYI, we noticed the below changes on
>> 
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> commit 63c6a211b0eb5b1c86ffdd9d89639fb7f1b70fca ("mm: workingset: per-cgroup cache thrash detection")
>> 
>> 
>> [    8.134495]   No soundcards found.
>> [    8.137598] debug: unmapping init [mem 0xffffffff81cdc000-0xffffffff81d99fff]
>> [    8.137598] debug: unmapping init [mem 0xffffffff81cdc000-0xffffffff81d99fff]
>> [    8.155388] BUG: sleeping function called from invalid context at mm/memory.c:1207
>> [    8.155388] BUG: sleeping function called from invalid context at mm/memory.c:1207
>> [    8.158212] in_atomic(): 0, irqs_disabled(): 0, pid: 79, name: mount
>> [    8.158212] in_atomic(): 0, irqs_disabled(): 0, pid: 79, name: mount
>> [    8.160436] 1 lock held by mount/79:
>> [    8.160436] 1 lock held by mount/79:
>> [    8.161488]  #0: 
>> [ 8.161488] #0: ( (rcu_read_lockrcu_read_lock){......}){......}, at:
>> , at: [<ffffffff810e4cc9>] rcu_lock_acquire+0x0/0x20
>> [<ffffffff810e4cc9>] rcu_lock_acquire+0x0/0x20
>> [    8.164136] Preemption disabled at:
>> [    8.164136] Preemption disabled at:[<ffffffff8106a358>] vprintk_default+0x18/0x1a
>> [<ffffffff8106a358>] vprintk_default+0x18/0x1a
>
> I'm not sure why this is pointing at vprintk_default...
>
> mm-workingset-per-cgroup-cache-thrash-detection.patch does have a bug
> which could cause this.  It's fixed by
> mm-workingset-per-cgroup-cache-thrash-detection-fix.patch.  Was the
> -fix patch applied during this testing?

The original test is for linux-next tree of 2016-02-03, which hasn't the
fix patch.  The fix patch is merged by linux-next 2016-02-04.  I queued
the same test for the fix patch and there is no such bug as above.

Best Regards,
Huang, Ying

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web