All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Allison Henderson <allison.henderson@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [allisonhenderson-xfs_work:delayed_attrs_v21_extended 39/62] fs/xfs/xfs_attr_item.c:292:1: sparse: sparse: symbol 'xfs_trans_attr_finish_update' was not declared. Should it be static?
Date: Mon, 19 Jul 2021 11:44:40 +0800	[thread overview]
Message-ID: <202107191127.kQqGprKw-lkp@intel.com> (raw)

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

tree:   https://github.com/allisonhenderson/xfs_work.git delayed_attrs_v21_extended
head:   1a71ced599b41e7ee9f0ea02427b76c30f71f7dd
commit: ba1114fc490c84643980a816cfc54ae8f5da1dd3 [39/62] xfs: Implement attr logging and replay
config: x86_64-randconfig-s021-20210718 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-341-g8af24329-dirty
        # https://github.com/allisonhenderson/xfs_work/commit/ba1114fc490c84643980a816cfc54ae8f5da1dd3
        git remote add allisonhenderson-xfs_work https://github.com/allisonhenderson/xfs_work.git
        git fetch --no-tags allisonhenderson-xfs_work delayed_attrs_v21_extended
        git checkout ba1114fc490c84643980a816cfc54ae8f5da1dd3
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash

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


sparse warnings: (new ones prefixed by >>)
>> fs/xfs/xfs_attr_item.c:292:1: sparse: sparse: symbol 'xfs_trans_attr_finish_update' was not declared. Should it be static?
>> fs/xfs/xfs_attr_item.c:496:27: sparse: sparse: symbol 'xfs_trans_get_attrd' was not declared. Should it be static?
>> fs/xfs/xfs_attr_item.c:608:30: sparse: sparse: Using plain integer as NULL pointer
   fs/xfs/xfs_attr_item.c: note: in included file:
   fs/xfs/xfs_log.h:34:21: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be32 [usertype] oh_len @@     got int len @@
   fs/xfs/xfs_log.h:34:21: sparse:     expected restricted __be32 [usertype] oh_len
   fs/xfs/xfs_log.h:34:21: sparse:     got int len
   fs/xfs/xfs_log.h:34:21: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be32 [usertype] oh_len @@     got int len @@
   fs/xfs/xfs_log.h:34:21: sparse:     expected restricted __be32 [usertype] oh_len
   fs/xfs/xfs_log.h:34:21: sparse:     got int len
   fs/xfs/xfs_log.h:34:21: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be32 [usertype] oh_len @@     got int len @@
   fs/xfs/xfs_log.h:34:21: sparse:     expected restricted __be32 [usertype] oh_len
   fs/xfs/xfs_log.h:34:21: sparse:     got int len
   fs/xfs/xfs_log.h:34:21: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be32 [usertype] oh_len @@     got int len @@
   fs/xfs/xfs_log.h:34:21: sparse:     expected restricted __be32 [usertype] oh_len
   fs/xfs/xfs_log.h:34:21: sparse:     got int len

Please review and possibly fold the followup patch.

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

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [allisonhenderson-xfs_work:delayed_attrs_v21_extended 39/62] fs/xfs/xfs_attr_item.c:292:1: sparse: sparse: symbol 'xfs_trans_attr_finish_update' was not declared. Should it be static?
Date: Mon, 19 Jul 2021 11:44:40 +0800	[thread overview]
Message-ID: <202107191127.kQqGprKw-lkp@intel.com> (raw)

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

tree:   https://github.com/allisonhenderson/xfs_work.git delayed_attrs_v21_extended
head:   1a71ced599b41e7ee9f0ea02427b76c30f71f7dd
commit: ba1114fc490c84643980a816cfc54ae8f5da1dd3 [39/62] xfs: Implement attr logging and replay
config: x86_64-randconfig-s021-20210718 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-341-g8af24329-dirty
        # https://github.com/allisonhenderson/xfs_work/commit/ba1114fc490c84643980a816cfc54ae8f5da1dd3
        git remote add allisonhenderson-xfs_work https://github.com/allisonhenderson/xfs_work.git
        git fetch --no-tags allisonhenderson-xfs_work delayed_attrs_v21_extended
        git checkout ba1114fc490c84643980a816cfc54ae8f5da1dd3
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash

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


sparse warnings: (new ones prefixed by >>)
>> fs/xfs/xfs_attr_item.c:292:1: sparse: sparse: symbol 'xfs_trans_attr_finish_update' was not declared. Should it be static?
>> fs/xfs/xfs_attr_item.c:496:27: sparse: sparse: symbol 'xfs_trans_get_attrd' was not declared. Should it be static?
>> fs/xfs/xfs_attr_item.c:608:30: sparse: sparse: Using plain integer as NULL pointer
   fs/xfs/xfs_attr_item.c: note: in included file:
   fs/xfs/xfs_log.h:34:21: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be32 [usertype] oh_len @@     got int len @@
   fs/xfs/xfs_log.h:34:21: sparse:     expected restricted __be32 [usertype] oh_len
   fs/xfs/xfs_log.h:34:21: sparse:     got int len
   fs/xfs/xfs_log.h:34:21: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be32 [usertype] oh_len @@     got int len @@
   fs/xfs/xfs_log.h:34:21: sparse:     expected restricted __be32 [usertype] oh_len
   fs/xfs/xfs_log.h:34:21: sparse:     got int len
   fs/xfs/xfs_log.h:34:21: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be32 [usertype] oh_len @@     got int len @@
   fs/xfs/xfs_log.h:34:21: sparse:     expected restricted __be32 [usertype] oh_len
   fs/xfs/xfs_log.h:34:21: sparse:     got int len
   fs/xfs/xfs_log.h:34:21: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be32 [usertype] oh_len @@     got int len @@
   fs/xfs/xfs_log.h:34:21: sparse:     expected restricted __be32 [usertype] oh_len
   fs/xfs/xfs_log.h:34:21: sparse:     got int len

Please review and possibly fold the followup patch.

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

             reply	other threads:[~2021-07-19  3:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  3:44 kernel test robot [this message]
2021-07-19  3:44 ` [allisonhenderson-xfs_work:delayed_attrs_v21_extended 39/62] fs/xfs/xfs_attr_item.c:292:1: sparse: sparse: symbol 'xfs_trans_attr_finish_update' was not declared. Should it be static? kernel test robot
2021-07-19  3:44 ` [RFC PATCH allisonhenderson-xfs_work] xfs: xfs_trans_attr_finish_update can be static kernel test robot
2021-07-19  3:44   ` 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=202107191127.kQqGprKw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=allison.henderson@oracle.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.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.