All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [djwong-xfs:vectorized-scrub 198/299] fs/xfs/./xfs_trace.h:1380:4: error: 'XFS_RTLOCK_ALLOC' undeclared; did you mean 'XFS_RTBLOCKLOG'?
Date: Sun, 08 Aug 2021 06:57:22 +0800	[thread overview]
Message-ID: <202108080653.OPnuMeUm-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git vectorized-scrub
head:   5fc557f566b4196e3c3c77271840ba84bf158d3b
commit: fe4bf9efa3c4ee2c158b68ec9074a112b4653389 [198/299] xfs: refactor realtime inode locking
config: i386-randconfig-c021-20210804 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?id=fe4bf9efa3c4ee2c158b68ec9074a112b4653389
        git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
        git fetch --no-tags djwong-xfs vectorized-scrub
        git checkout fe4bf9efa3c4ee2c158b68ec9074a112b4653389
        # save the attached .config to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from include/trace/define_trace.h:102,
                    from fs/xfs/xfs_trace.h:4512,
                    from fs/xfs/xfs_trace.c:44:
   fs/xfs/./xfs_trace.h: In function 'trace_raw_output_xfs_rtlock_class':
>> fs/xfs/./xfs_trace.h:1380:4: error: 'XFS_RTLOCK_ALLOC' undeclared (first use in this function); did you mean 'XFS_RTBLOCKLOG'?
    1380 |  { XFS_RTLOCK_ALLOC,  "rbm|rsum" }
         |    ^~~~~~~~~~~~~~~~
   include/trace/trace_events.h:393:27: note: in definition of macro 'DECLARE_EVENT_CLASS'
     393 |  trace_event_printf(iter, print);    \
         |                           ^~~~~
   fs/xfs/./xfs_trace.h:1393:2: note: in expansion of macro 'TP_printk'
    1393 |  TP_printk("dev %d:%d flags %s",
         |  ^~~~~~~~~
   fs/xfs/./xfs_trace.h:1395:5: note: in expansion of macro '__print_flags'
    1395 |     __print_flags(__entry->flags, "|", XFS_RTLOCK_STRINGS))
         |     ^~~~~~~~~~~~~
   fs/xfs/./xfs_trace.h:1395:40: note: in expansion of macro 'XFS_RTLOCK_STRINGS'
    1395 |     __print_flags(__entry->flags, "|", XFS_RTLOCK_STRINGS))
         |                                        ^~~~~~~~~~~~~~~~~~
   fs/xfs/./xfs_trace.h:1380:4: note: each undeclared identifier is reported only once for each function it appears in
    1380 |  { XFS_RTLOCK_ALLOC,  "rbm|rsum" }
         |    ^~~~~~~~~~~~~~~~
   include/trace/trace_events.h:393:27: note: in definition of macro 'DECLARE_EVENT_CLASS'
     393 |  trace_event_printf(iter, print);    \
         |                           ^~~~~
   fs/xfs/./xfs_trace.h:1393:2: note: in expansion of macro 'TP_printk'
    1393 |  TP_printk("dev %d:%d flags %s",
         |  ^~~~~~~~~
   fs/xfs/./xfs_trace.h:1395:5: note: in expansion of macro '__print_flags'
    1395 |     __print_flags(__entry->flags, "|", XFS_RTLOCK_STRINGS))
         |     ^~~~~~~~~~~~~
   fs/xfs/./xfs_trace.h:1395:40: note: in expansion of macro 'XFS_RTLOCK_STRINGS'
    1395 |     __print_flags(__entry->flags, "|", XFS_RTLOCK_STRINGS))
         |                                        ^~~~~~~~~~~~~~~~~~


vim +1380 fs/xfs/./xfs_trace.h

  1378	
  1379	#define XFS_RTLOCK_STRINGS \
> 1380		{ XFS_RTLOCK_ALLOC,		"rbm|rsum" }
  1381	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

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

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: kbuild-all@lists.01.org,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: [djwong-xfs:vectorized-scrub 198/299] fs/xfs/./xfs_trace.h:1380:4: error: 'XFS_RTLOCK_ALLOC' undeclared; did you mean 'XFS_RTBLOCKLOG'?
Date: Sun, 8 Aug 2021 06:57:22 +0800	[thread overview]
Message-ID: <202108080653.OPnuMeUm-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git vectorized-scrub
head:   5fc557f566b4196e3c3c77271840ba84bf158d3b
commit: fe4bf9efa3c4ee2c158b68ec9074a112b4653389 [198/299] xfs: refactor realtime inode locking
config: i386-randconfig-c021-20210804 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?id=fe4bf9efa3c4ee2c158b68ec9074a112b4653389
        git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
        git fetch --no-tags djwong-xfs vectorized-scrub
        git checkout fe4bf9efa3c4ee2c158b68ec9074a112b4653389
        # save the attached .config to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from include/trace/define_trace.h:102,
                    from fs/xfs/xfs_trace.h:4512,
                    from fs/xfs/xfs_trace.c:44:
   fs/xfs/./xfs_trace.h: In function 'trace_raw_output_xfs_rtlock_class':
>> fs/xfs/./xfs_trace.h:1380:4: error: 'XFS_RTLOCK_ALLOC' undeclared (first use in this function); did you mean 'XFS_RTBLOCKLOG'?
    1380 |  { XFS_RTLOCK_ALLOC,  "rbm|rsum" }
         |    ^~~~~~~~~~~~~~~~
   include/trace/trace_events.h:393:27: note: in definition of macro 'DECLARE_EVENT_CLASS'
     393 |  trace_event_printf(iter, print);    \
         |                           ^~~~~
   fs/xfs/./xfs_trace.h:1393:2: note: in expansion of macro 'TP_printk'
    1393 |  TP_printk("dev %d:%d flags %s",
         |  ^~~~~~~~~
   fs/xfs/./xfs_trace.h:1395:5: note: in expansion of macro '__print_flags'
    1395 |     __print_flags(__entry->flags, "|", XFS_RTLOCK_STRINGS))
         |     ^~~~~~~~~~~~~
   fs/xfs/./xfs_trace.h:1395:40: note: in expansion of macro 'XFS_RTLOCK_STRINGS'
    1395 |     __print_flags(__entry->flags, "|", XFS_RTLOCK_STRINGS))
         |                                        ^~~~~~~~~~~~~~~~~~
   fs/xfs/./xfs_trace.h:1380:4: note: each undeclared identifier is reported only once for each function it appears in
    1380 |  { XFS_RTLOCK_ALLOC,  "rbm|rsum" }
         |    ^~~~~~~~~~~~~~~~
   include/trace/trace_events.h:393:27: note: in definition of macro 'DECLARE_EVENT_CLASS'
     393 |  trace_event_printf(iter, print);    \
         |                           ^~~~~
   fs/xfs/./xfs_trace.h:1393:2: note: in expansion of macro 'TP_printk'
    1393 |  TP_printk("dev %d:%d flags %s",
         |  ^~~~~~~~~
   fs/xfs/./xfs_trace.h:1395:5: note: in expansion of macro '__print_flags'
    1395 |     __print_flags(__entry->flags, "|", XFS_RTLOCK_STRINGS))
         |     ^~~~~~~~~~~~~
   fs/xfs/./xfs_trace.h:1395:40: note: in expansion of macro 'XFS_RTLOCK_STRINGS'
    1395 |     __print_flags(__entry->flags, "|", XFS_RTLOCK_STRINGS))
         |                                        ^~~~~~~~~~~~~~~~~~


vim +1380 fs/xfs/./xfs_trace.h

  1378	
  1379	#define XFS_RTLOCK_STRINGS \
> 1380		{ XFS_RTLOCK_ALLOC,		"rbm|rsum" }
  1381	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

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

             reply	other threads:[~2021-08-07 22:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-07 22:57 kernel test robot [this message]
2021-08-07 22:57 ` [djwong-xfs:vectorized-scrub 198/299] fs/xfs/./xfs_trace.h:1380:4: error: 'XFS_RTLOCK_ALLOC' undeclared; did you mean 'XFS_RTBLOCKLOG'? kernel test robot

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=202108080653.OPnuMeUm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.