mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Yang Shi <yang.s@alibaba-inc.com>
Cc: kbuild-all@01.org, cl@linux.com, penberg@kernel.org,
	rientjes@google.com, iamjoonsoo.kim@lge.com,
	akpm@linux-foundation.org, mhocko@kernel.org,
	Yang Shi <yang.s@alibaba-inc.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory
Date: Sat, 7 Oct 2017 21:05:04 +0800	[thread overview]
Message-ID: <201710072053.sdlTJ3hP%fengguang.wu@intel.com> (raw)
In-Reply-To: <1507152550-46205-4-git-send-email-yang.s@alibaba-inc.com>

[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]

Hi Yang,

[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.14-rc3 next-20170929]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Yang-Shi/oom-capture-unreclaimable-slab-info-in-oom-message/20171007-173639
base:   git://git.cmpxchg.org/linux-mmotm.git master
config: h8300-h8300h-sim_defconfig (attached as .config)
compiler: h8300-linux-gcc (GCC) 6.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=h8300 

All errors (new ones prefixed by >>):

   mm/slab_common.o: In function `dump_unreclaimable_slab':
>> mm/slab_common.c:1298: undefined reference to `get_slabinfo'

vim +1298 mm/slab_common.c

  1272	
  1273	void dump_unreclaimable_slab(void)
  1274	{
  1275		struct kmem_cache *s, *s2;
  1276		struct slabinfo sinfo;
  1277	
  1278		/*
  1279		 * Here acquiring slab_mutex is risky since we don't prefer to get
  1280		 * sleep in oom path. But, without mutex hold, it may introduce a
  1281		 * risk of crash.
  1282		 * Use mutex_trylock to protect the list traverse, dump nothing
  1283		 * without acquiring the mutex.
  1284		 */
  1285		if (!mutex_trylock(&slab_mutex)) {
  1286			pr_warn("excessive unreclaimable slab but cannot dump stats\n");
  1287			return;
  1288		}
  1289	
  1290		pr_info("Unreclaimable slab info:\n");
  1291		pr_info("Name                      Used          Total\n");
  1292	
  1293		list_for_each_entry_safe(s, s2, &slab_caches, list) {
  1294			if (!is_root_cache(s) || (s->flags & SLAB_RECLAIM_ACCOUNT))
  1295				continue;
  1296	
  1297			memset(&sinfo, 0, sizeof(sinfo));
> 1298			get_slabinfo(s, &sinfo);
  1299	
  1300			if (sinfo.num_objs > 0)
  1301				pr_info("%-17s %10luKB %10luKB\n", cache_name(s),
  1302					(sinfo.active_objs * s->size) / 1024,
  1303					(sinfo.num_objs * s->size) / 1024);
  1304		}
  1305		mutex_unlock(&slab_mutex);
  1306	}
  1307	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 4722 bytes --]

  parent reply	other threads:[~2017-10-07 13:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 21:29 [PATCH 0/3 v10] oom: capture unreclaimable slab info in oom message Yang Shi
2017-10-04 21:29 ` [PATCH 1/3] tools: slabinfo: add "-U" option to show unreclaimable slabs only Yang Shi
2017-10-04 21:29 ` [PATCH 2/3] mm: slabinfo: dump CONFIG_SLABINFO Yang Shi
2017-10-07 11:45   ` kbuild test robot
2017-10-07 12:06   ` kbuild test robot
2017-10-04 21:29 ` [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory Yang Shi
2017-10-06  9:37   ` Michal Hocko
2017-10-06 16:37     ` Yang Shi
2017-10-09  6:33       ` Michal Hocko
2017-10-09  6:36         ` Michal Hocko
2017-10-09 16:44           ` Yang Shi
2017-10-09 18:53           ` Yang Shi
2017-10-09 21:00             ` Yang Shi
2017-10-07 10:10   ` kbuild test robot
2017-10-07 13:05   ` kbuild test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-10 17:25 [PATCH 0/3 v11] oom: capture unreclaimable slab info in oom message Yang Shi
2017-10-10 17:25 ` [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory Yang Shi
2017-10-17  0:15   ` David Rientjes
2017-10-17  7:44     ` Michal Hocko
2017-10-17 20:59       ` David Rientjes
2017-10-17 21:40         ` Yang Shi
2017-10-17 21:50           ` David Rientjes
2017-10-17 22:20             ` Yang Shi
2017-10-17 22:39               ` David Rientjes
2017-10-18 19:09                 ` Yang Shi
2017-10-19  7:28                 ` Michal Hocko
2017-10-19 23:12                   ` Yang Shi
2017-10-03 18:06 [PATCH 0/3 v8] oom: capture unreclaimable slab info in oom message Yang Shi
2017-10-03 18:06 ` [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory Yang Shi
2017-10-04 14:27   ` Michal Hocko
2017-10-04 17:37     ` Yang Shi
2017-10-04 18:08     ` Yang Shi
2017-10-05  7:57       ` Michal Hocko

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=201710072053.sdlTJ3hP%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=yang.s@alibaba-inc.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

all inboxes | Powered by JetHome®