public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Vincent Donnefort <vdonnefort@google.com>,
	rostedt@goodmis.org, mhiramat@kernel.org,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, mathieu.desnoyers@efficios.com,
	kernel-team@android.com,
	Vincent Donnefort <vdonnefort@google.com>
Subject: Re: [PATCH v17 2/6] ring-buffer: Introducing ring-buffer mapping functions
Date: Wed, 14 Feb 2024 18:26:49 +0800	[thread overview]
Message-ID: <202402141856.fVl4pCHi-lkp@intel.com> (raw)
In-Reply-To: <20240213114945.3528801-3-vdonnefort@google.com>

Hi Vincent,

kernel test robot noticed the following build errors:

[auto build test ERROR on ca185770db914869ff9fe773bac5e0e5e4165b83]

url:    https://github.com/intel-lab-lkp/linux/commits/Vincent-Donnefort/ring-buffer-Zero-ring-buffer-sub-buffers/20240213-195302
base:   ca185770db914869ff9fe773bac5e0e5e4165b83
patch link:    https://lore.kernel.org/r/20240213114945.3528801-3-vdonnefort%40google.com
patch subject: [PATCH v17 2/6] ring-buffer: Introducing ring-buffer mapping functions
config: x86_64-randconfig-161-20240214 (https://download.01.org/0day-ci/archive/20240214/202402141856.fVl4pCHi-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240214/202402141856.fVl4pCHi-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202402141856.fVl4pCHi-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from arch/x86/include/asm/bug.h:87,
                    from include/linux/bug.h:5,
                    from include/linux/jump_label.h:256,
                    from arch/x86/include/asm/string_64.h:6,
                    from arch/x86/include/asm/string.h:5,
                    from include/linux/string.h:61,
                    from include/linux/bitmap.h:12,
                    from include/linux/cpumask.h:12,
                    from include/linux/interrupt.h:8,
                    from include/linux/trace_recursion.h:5,
                    from kernel/trace/ring_buffer.c:7:
   kernel/trace/ring_buffer.c: In function '__rb_inc_dec_mapped':
>> include/linux/lockdep.h:234:52: error: invalid type argument of '->' (have 'struct mutex')
     234 | #define lockdep_is_held(lock)  lock_is_held(&(lock)->dep_map)
         |                                                    ^~
   include/asm-generic/bug.h:123:25: note: in definition of macro 'WARN_ON'
     123 |  int __ret_warn_on = !!(condition);    \
         |                         ^~~~~~~~~
   include/linux/lockdep.h:267:2: note: in expansion of macro 'lockdep_assert'
     267 |  lockdep_assert(lockdep_is_held(l) != LOCK_STATE_NOT_HELD)
         |  ^~~~~~~~~~~~~~
   include/linux/lockdep.h:267:17: note: in expansion of macro 'lockdep_is_held'
     267 |  lockdep_assert(lockdep_is_held(l) != LOCK_STATE_NOT_HELD)
         |                 ^~~~~~~~~~~~~~~
   kernel/trace/ring_buffer.c:6185:2: note: in expansion of macro 'lockdep_assert_held'
    6185 |  lockdep_assert_held(cpu_buffer->mapping_lock);
         |  ^~~~~~~~~~~~~~~~~~~


vim +234 include/linux/lockdep.h

f607c668577481 Peter Zijlstra 2009-07-20  233  
f8319483f57f1c Peter Zijlstra 2016-11-30 @234  #define lockdep_is_held(lock)		lock_is_held(&(lock)->dep_map)
f8319483f57f1c Peter Zijlstra 2016-11-30  235  #define lockdep_is_held_type(lock, r)	lock_is_held_type(&(lock)->dep_map, (r))
f607c668577481 Peter Zijlstra 2009-07-20  236  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2024-02-14 10:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 11:49 [PATCH v17 0/6] Introducing trace buffer mapping by user-space Vincent Donnefort
2024-02-13 11:49 ` [PATCH v17 1/6] ring-buffer: Zero ring-buffer sub-buffers Vincent Donnefort
2024-02-13 11:49 ` [PATCH v17 2/6] ring-buffer: Introducing ring-buffer mapping functions Vincent Donnefort
2024-02-13 20:53   ` Steven Rostedt
2024-02-13 22:51     ` Steven Rostedt
2024-02-14  1:23   ` kernel test robot
2024-02-14 10:26   ` kernel test robot [this message]
2024-02-13 11:49 ` [PATCH v17 3/6] tracing: Add snapshot refcount Vincent Donnefort
2024-02-19 18:17   ` Steven Rostedt
2024-02-19 18:22     ` Steven Rostedt
2024-02-13 11:49 ` [PATCH v17 4/6] tracing: Allow user-space mapping of the ring-buffer Vincent Donnefort
2024-02-13 11:49 ` [PATCH v17 5/6] Documentation: tracing: Add ring-buffer mapping Vincent Donnefort
2024-02-13 11:49 ` [PATCH v17 6/6] ring-buffer/selftest: Add ring-buffer mapping test Vincent Donnefort

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=202402141856.fVl4pCHi-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=vdonnefort@google.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