From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752040AbcBEBvK (ORCPT <rfc822;w@1wt.eu>);
	Thu, 4 Feb 2016 20:51:10 -0500
Received: from mga04.intel.com ([192.55.52.120]:12817 "EHLO mga04.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750736AbcBEBvI (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 4 Feb 2016 20:51:08 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.22,398,1449561600"; 
   d="scan'208";a="42754889"
From: "Huang\, Ying" <ying.huang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
        Vladimir Davydov <vdavydov@virtuozzo.com>,
        Johannes Weiner <hannes@cmpxchg.org>,
        LKML <linux-kernel@vger.kernel.org>, Michal Hocko <mhocko@suse.cz>,
        David Rientjes <rientjes@google.com>, <lkp@01.org>
Subject: Re: [LKP] [lkp] [mm] 63c6a211b0: BUG: sleeping function called from invalid context at mm/memory.c:1207
References: <87io25e20k.fsf@yhuang-dev.intel.com>
	<20160204132958.f8571de90d56749336c9af05@linux-foundation.org>
Date: Fri, 05 Feb 2016 09:51:06 +0800
In-Reply-To: <20160204132958.f8571de90d56749336c9af05@linux-foundation.org>
	(Andrew Morton's message of "Thu, 4 Feb 2016 13:29:58 -0800")
Message-ID: <8760y3aprp.fsf@yhuang-dev.intel.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=ascii
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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