From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
David Rientjes <rientjes@google.com>,
Michal Hocko <mhocko@suse.cz>,
Vladimir Davydov <vdavydov@virtuozzo.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [lkp] [mm] 63c6a211b0: BUG: sleeping function called from invalid context at mm/memory.c:1207
Date: Thu, 4 Feb 2016 13:29:58 -0800 [thread overview]
Message-ID: <20160204132958.f8571de90d56749336c9af05@linux-foundation.org> (raw)
In-Reply-To: <87io25e20k.fsf@yhuang-dev.intel.com>
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?
next prev parent reply other threads:[~2016-02-04 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 0:46 [lkp] [mm] 63c6a211b0: BUG: sleeping function called from invalid context at mm/memory.c:1207 kernel test robot
2016-02-04 21:29 ` Andrew Morton [this message]
2016-02-05 1:51 ` [LKP] " Huang, Ying
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=20160204132958.f8571de90d56749336c9af05@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mhocko@suse.cz \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.au \
--cc=vdavydov@virtuozzo.com \
--cc=ying.huang@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).