public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@01.org, Josh Poimboeuf <jpoimboe@redhat.com>,
	Ingo Molnar <mingo@kernel.org>,
	Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/x86/intel: Fix unwind errors from PEBS entries (mk-II)
Date: Fri, 20 Jul 2018 06:45:09 +0800	[thread overview]
Message-ID: <201807200644.BeK4RHQU%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180719211954.GZ2512@hirez.programming.kicks-ass.net>

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

Hi Peter,

I love your patch! Perhaps something to improve:

[auto build test WARNING on tip/perf/core]
[also build test WARNING on v4.18-rc5 next-20180719]
[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/Peter-Zijlstra/perf-x86-intel-Fix-unwind-errors-from-PEBS-entries-mk-II/20180720-061741
config: i386-randconfig-x008-201828 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   In file included from include/linux/perf_event.h:17:0,
                    from include/linux/trace_events.h:10,
                    from include/trace/trace_events.h:20,
                    from include/trace/define_trace.h:96,
                    from include/trace/events/mce.h:75,
                    from arch/x86/kernel/cpu/mcheck/mce.c:63:
>> include/uapi/linux/perf_event.h:147:39: warning: left shift count >= width of type [-Wshift-count-overflow]
     __PERF_SAMPLE_CALLCHAIN_EARLY  = 1UL << 63,
                                          ^~

vim +147 include/uapi/linux/perf_event.h

   118	
   119	/*
   120	 * Bits that can be set in attr.sample_type to request information
   121	 * in the overflow packets.
   122	 */
   123	enum perf_event_sample_format {
   124		PERF_SAMPLE_IP				= 1U << 0,
   125		PERF_SAMPLE_TID				= 1U << 1,
   126		PERF_SAMPLE_TIME			= 1U << 2,
   127		PERF_SAMPLE_ADDR			= 1U << 3,
   128		PERF_SAMPLE_READ			= 1U << 4,
   129		PERF_SAMPLE_CALLCHAIN			= 1U << 5,
   130		PERF_SAMPLE_ID				= 1U << 6,
   131		PERF_SAMPLE_CPU				= 1U << 7,
   132		PERF_SAMPLE_PERIOD			= 1U << 8,
   133		PERF_SAMPLE_STREAM_ID			= 1U << 9,
   134		PERF_SAMPLE_RAW				= 1U << 10,
   135		PERF_SAMPLE_BRANCH_STACK		= 1U << 11,
   136		PERF_SAMPLE_REGS_USER			= 1U << 12,
   137		PERF_SAMPLE_STACK_USER			= 1U << 13,
   138		PERF_SAMPLE_WEIGHT			= 1U << 14,
   139		PERF_SAMPLE_DATA_SRC			= 1U << 15,
   140		PERF_SAMPLE_IDENTIFIER			= 1U << 16,
   141		PERF_SAMPLE_TRANSACTION			= 1U << 17,
   142		PERF_SAMPLE_REGS_INTR			= 1U << 18,
   143		PERF_SAMPLE_PHYS_ADDR			= 1U << 19,
   144	
   145		PERF_SAMPLE_MAX = 1U << 20,		/* non-ABI */
   146	
 > 147		__PERF_SAMPLE_CALLCHAIN_EARLY		= 1UL << 63,
   148	};
   149	

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

  reply	other threads:[~2018-07-19 22:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19  4:33 BUG: KASAN: stack-out-of-bounds in unwind_next_frame Prashant Bhole
2018-07-19 15:33 ` Josh Poimboeuf
2018-07-19 17:43   ` Peter Zijlstra
2018-07-19 21:19     ` [PATCH] perf/x86/intel: Fix unwind errors from PEBS entries (mk-II) Peter Zijlstra
2018-07-19 22:45       ` kbuild test robot [this message]
2018-07-19 23:54       ` kbuild test robot
2018-07-23 13:30       ` Josh Poimboeuf
2018-07-23 14:14         ` Peter Zijlstra
2018-07-24 16:35           ` Josh Poimboeuf
2018-08-06 15:35       ` Fubo Chen
2018-08-06 15:42         ` Peter Zijlstra
2018-08-06 16:54           ` Fubo Chen
2018-08-06 18:04             ` Peter Zijlstra
2018-08-06 21:28               ` Fubo Chen
2018-08-06 22:30                 ` Peter Zijlstra
2018-08-06 23:04                   ` Fubo Chen
2018-08-07  9:05                     ` Peter Zijlstra

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=201807200644.BeK4RHQU%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bhole_prashant_q7@lab.ntt.co.jp \
    --cc=jpoimboe@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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