From: kernel test robot <lkp@intel.com>
To: Mike Snitzer <snitzer@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Matthew Sakai <msakai@redhat.com>
Subject: drivers/md/dm-vdo/int-map.c:87: error: Cannot parse struct or union!
Date: Tue, 28 May 2024 04:02:40 +0800 [thread overview]
Message-ID: <202405280322.DuFLX7rb-lkp@intel.com> (raw)
Hi Mike,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 2bfcfd584ff5ccc8bb7acde19b42570414bf880b
commit: f36b1d3ba533d21b5b793623f05761b0297d114e dm vdo: use a proper Makefile for dm-vdo
date: 3 months ago
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20240528/202405280322.DuFLX7rb-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project bafda89a0944d947fc4b3b5663185e07a397ac30)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240528/202405280322.DuFLX7rb-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/202405280322.DuFLX7rb-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/md/dm-vdo/int-map.c:87: error: Cannot parse struct or union!
drivers/md/dm-vdo/int-map.c:105: warning: Function parameter or struct member 'bucket_count' not described in 'int_map'
drivers/md/dm-vdo/int-map.c:330: warning: Function parameter or struct member '__always_unused' not described in 'search_hop_list'
drivers/md/dm-vdo/int-map.c:330: warning: Excess function parameter 'map' description in 'search_hop_list'
drivers/md/dm-vdo/int-map.c:461: warning: Function parameter or struct member '__always_unused' not described in 'move_empty_bucket'
drivers/md/dm-vdo/int-map.c:461: warning: Excess function parameter 'map' description in 'move_empty_bucket'
vim +87 drivers/md/dm-vdo/int-map.c
cc46b9554b3f6d Matthew Sakai 2023-11-16 66
cc46b9554b3f6d Matthew Sakai 2023-11-16 67 /**
cc46b9554b3f6d Matthew Sakai 2023-11-16 68 * struct bucket - hash bucket
cc46b9554b3f6d Matthew Sakai 2023-11-16 69 *
cc46b9554b3f6d Matthew Sakai 2023-11-16 70 * Buckets are packed together to reduce memory usage and improve cache efficiency. It would be
cc46b9554b3f6d Matthew Sakai 2023-11-16 71 * tempting to encode the hop offsets separately and maintain alignment of key/value pairs, but
cc46b9554b3f6d Matthew Sakai 2023-11-16 72 * it's crucial to keep the hop fields near the buckets that they use them so they'll tend to share
cc46b9554b3f6d Matthew Sakai 2023-11-16 73 * cache lines.
cc46b9554b3f6d Matthew Sakai 2023-11-16 74 */
cc46b9554b3f6d Matthew Sakai 2023-11-16 75 struct __packed bucket {
cc46b9554b3f6d Matthew Sakai 2023-11-16 76 /**
cc46b9554b3f6d Matthew Sakai 2023-11-16 77 * @first_hop: The biased offset of the first entry in the hop list of the neighborhood
cc46b9554b3f6d Matthew Sakai 2023-11-16 78 * that hashes to this bucket.
cc46b9554b3f6d Matthew Sakai 2023-11-16 79 */
cc46b9554b3f6d Matthew Sakai 2023-11-16 80 u8 first_hop;
cc46b9554b3f6d Matthew Sakai 2023-11-16 81 /** @next_hop: The biased offset of the next bucket in the hop list. */
cc46b9554b3f6d Matthew Sakai 2023-11-16 82 u8 next_hop;
cc46b9554b3f6d Matthew Sakai 2023-11-16 83 /** @key: The key stored in this bucket. */
cc46b9554b3f6d Matthew Sakai 2023-11-16 84 u64 key;
cc46b9554b3f6d Matthew Sakai 2023-11-16 85 /** @value: The value stored in this bucket (NULL if empty). */
cc46b9554b3f6d Matthew Sakai 2023-11-16 86 void *value;
cc46b9554b3f6d Matthew Sakai 2023-11-16 @87 };
cc46b9554b3f6d Matthew Sakai 2023-11-16 88
:::::: The code at line 87 was first introduced by commit
:::::: cc46b9554b3f6d2f09b1111386b2706e5b4f56c8 dm vdo: add basic hash map data structures
:::::: TO: Matthew Sakai <msakai@redhat.com>
:::::: CC: Mike Snitzer <snitzer@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-05-27 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 20:02 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-14 9:00 drivers/md/dm-vdo/int-map.c:87: error: Cannot parse struct or union! kernel test robot
2024-09-10 2:04 kernel test robot
2024-10-01 3:26 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=202405280322.DuFLX7rb-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=msakai@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=snitzer@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.