All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com
Subject: [tip:WIP.x86/stackguards 1/32] mm/slab.c:1486:27: error: expected '}' before ';' token
Date: Mon, 15 Apr 2019 06:29:03 +0800	[thread overview]
Message-ID: <201904150601.BamXs2ZP%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/stackguards
head:   310a7f5b0b42c6a8edeb74ae3289a98896e0e5c9
commit: 7552063baa017438f2bfd6060e0b949808acc812 [1/32] mm/slab: Fix broken stack trace storage
config: x86_64-randconfig-x003-201915 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        git checkout 7552063baa017438f2bfd6060e0b949808acc812
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   mm/slab.c: In function 'store_stackinfo':
>> mm/slab.c:1486:27: error: expected '}' before ';' token
       .max_entries = size - 4;
                              ^

vim +1486 mm/slab.c

  1468	
  1469	#ifdef CONFIG_DEBUG_PAGEALLOC
  1470	static void store_stackinfo(struct kmem_cache *cachep, unsigned long *addr,
  1471				    unsigned long caller)
  1472	{
  1473		int size = cachep->object_size / sizeof(unsigned long);
  1474	
  1475		addr = (unsigned long *)&((char *)addr)[obj_offset(cachep)];
  1476	
  1477		if (size < 5)
  1478			return;
  1479	
  1480		*addr++ = 0x12345678;
  1481		*addr++ = caller;
  1482		*addr++ = smp_processor_id();
  1483	#ifdef CONFIG_STACKTRACE
  1484		{
  1485			struct stack_trace trace = {
> 1486				.max_entries	= size - 4;
  1487				.entries	= addr;
  1488				.skip		= 3;
  1489			};
  1490	
  1491			save_stack_trace(&trace);
  1492			addr += trace.nr_entries;
  1493		}
  1494	#endif
  1495		*addr = 0x87654321;
  1496	}
  1497	

---
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: 29463 bytes --]

                 reply	other threads:[~2019-04-14 22:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201904150601.BamXs2ZP%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tipbuild@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.