linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jann Horn <jannh@google.com>
To: lkp@intel.com
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
	Linux-MM <linux-mm@kvack.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Oleg Nesterov <oleg@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	guro@fb.com, kemi.wang@intel.com,
	Kees Cook <keescook@chromium.org>,
	Christopher Lameter <cl@linux.com>
Subject: Re: [PATCH] mm/vmstat: fix outdated vmstat_text
Date: Mon, 1 Oct 2018 15:46:22 +0200	[thread overview]
Message-ID: <CAG48ez1kXs9_YZkqFJUpoLTH9DdLOd614NJJ+adgmh7rbGZcqQ@mail.gmail.com> (raw)
In-Reply-To: <201809291116.emGRuKoB%fengguang.wu@intel.com>

On Sat, Sep 29, 2018 at 5:07 AM kbuild test robot <lkp@intel.com> wrote:
>
> Hi Jann,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.19-rc5 next-20180928]
> [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/Jann-Horn/mm-vmstat-fix-outdated-vmstat_text/20180929-102147
> config: i386-randconfig-x005-201838 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386
>
> All error/warnings (new ones prefixed by >>):
>
>    In file included from include/linux/export.h:45:0,
>                     from include/linux/linkage.h:7,
>                     from include/linux/fs.h:5,
>                     from mm/vmstat.c:12:
>    mm/vmstat.c: In function 'vmstat_start':
> >> include/linux/compiler.h:358:38: error: call to '__compiletime_assert_1664' declared with attribute error: BUILD_BUG_ON failed: stat_items_size != ARRAY_SIZE(vmstat_text) * sizeof(unsigned long)

Nice. Looks like the 0day test bot indeed found another mismatch:

#ifdef CONFIG_DEBUG_TLBFLUSH
#ifdef CONFIG_SMP
       "nr_tlb_remote_flush",
       "nr_tlb_remote_flush_received",
#endif /* CONFIG_SMP */
       "nr_tlb_local_flush_all",
       "nr_tlb_local_flush_one",
#endif /* CONFIG_DEBUG_TLBFLUSH */

vs

#ifdef CONFIG_DEBUG_TLBFLUSH
               NR_TLB_REMOTE_FLUSH,    /* cpu tried to flush others' tlbs */
               NR_TLB_REMOTE_FLUSH_RECEIVED,/* cpu received ipi for flush */
               NR_TLB_LOCAL_FLUSH_ALL,
               NR_TLB_LOCAL_FLUSH_ONE,
#endif /* CONFIG_DEBUG_TLBFLUSH */

So if you build with CONFIG_VM_EVENT_COUNTERS=y &&
CONFIG_DEBUG_TLBFLUSH=y && CONFIG_SMP=n, vmstat output is bogus.

I like having my decisions to add asserts immediately validated by the
0day test bot. ^^

I'll send a v2 with that fixed up.

  reply	other threads:[~2018-10-01 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29  1:36 Jann Horn
2018-09-29  3:07 ` kbuild test robot
2018-10-01 13:46   ` Jann Horn [this message]
2018-10-03 16:29 ` Michal Hocko
2018-10-03 16:31   ` Jann Horn

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=CAG48ez1kXs9_YZkqFJUpoLTH9DdLOd614NJJ+adgmh7rbGZcqQ@mail.gmail.com \
    --to=jannh@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=dave@stgolabs.net \
    --cc=guro@fb.com \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=kemi.wang@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oleg@redhat.com \
    --cc=torvalds@linux-foundation.org \
    /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