From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kmo@daterainc.com>,
linux-bcachefs@vger.kernel.org, linux-bcache@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kent Overstreet <kmo@daterainc.com>,
Kees Cook <keescook@chromium.org>, Coly Li <colyli@suse.de>
Subject: Re: [PATCH] closures: CLOSURE_CALLBACK() to fix type punning
Date: Mon, 20 Nov 2023 15:58:40 +0800 [thread overview]
Message-ID: <202311201549.FNQyD6Xl-lkp@intel.com> (raw)
In-Reply-To: <20231120030729.3285278-1-kent.overstreet@linux.dev>
Hi Kent,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.7-rc2 next-20231120]
[cannot apply to kees/for-next/pstore kees/for-next/kspp]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Kent-Overstreet/closures-CLOSURE_CALLBACK-to-fix-type-punning/20231120-110920
base: linus/master
patch link: https://lore.kernel.org/r/20231120030729.3285278-1-kent.overstreet%40linux.dev
patch subject: [PATCH] closures: CLOSURE_CALLBACK() to fix type punning
config: x86_64-buildonly-randconfig-005-20231120 (https://download.01.org/0day-ci/archive/20231120/202311201549.FNQyD6Xl-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231120/202311201549.FNQyD6Xl-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/202311201549.FNQyD6Xl-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/md/bcache/request.c:309: warning: Function parameter or member 'bch_data_insert' not described in 'CLOSURE_CALLBACK'
>> drivers/md/bcache/request.c:309: warning: expecting prototype for bch_data_insert(). Prototype was for CLOSURE_CALLBACK() instead
vim +309 drivers/md/bcache/request.c
cafe563591446c Kent Overstreet 2013-03-23 287
cafe563591446c Kent Overstreet 2013-03-23 288 /**
a34a8bfd4e6358 Kent Overstreet 2013-10-24 289 * bch_data_insert - stick some data in the cache
47344e330eabc1 Bart Van Assche 2018-03-18 290 * @cl: closure pointer.
cafe563591446c Kent Overstreet 2013-03-23 291 *
cafe563591446c Kent Overstreet 2013-03-23 292 * This is the starting point for any data to end up in a cache device; it could
cafe563591446c Kent Overstreet 2013-03-23 293 * be from a normal write, or a writeback write, or a write to a flash only
cafe563591446c Kent Overstreet 2013-03-23 294 * volume - it's also used by the moving garbage collector to compact data in
cafe563591446c Kent Overstreet 2013-03-23 295 * mostly empty buckets.
cafe563591446c Kent Overstreet 2013-03-23 296 *
cafe563591446c Kent Overstreet 2013-03-23 297 * It first writes the data to the cache, creating a list of keys to be inserted
cafe563591446c Kent Overstreet 2013-03-23 298 * (if the data had to be fragmented there will be multiple keys); after the
cafe563591446c Kent Overstreet 2013-03-23 299 * data is written it calls bch_journal, and after the keys have been added to
cafe563591446c Kent Overstreet 2013-03-23 300 * the next journal write they're inserted into the btree.
cafe563591446c Kent Overstreet 2013-03-23 301 *
3db4d0783eaf2a Shenghui Wang 2018-12-13 302 * It inserts the data in op->bio; bi_sector is used for the key offset,
cafe563591446c Kent Overstreet 2013-03-23 303 * and op->inode is used for the key inode.
cafe563591446c Kent Overstreet 2013-03-23 304 *
3db4d0783eaf2a Shenghui Wang 2018-12-13 305 * If op->bypass is true, instead of inserting the data it invalidates the
3db4d0783eaf2a Shenghui Wang 2018-12-13 306 * region of the cache represented by op->bio and op->inode.
cafe563591446c Kent Overstreet 2013-03-23 307 */
b945f655e6185e Kent Overstreet 2023-11-19 308 CLOSURE_CALLBACK(bch_data_insert)
cafe563591446c Kent Overstreet 2013-03-23 @309 {
b945f655e6185e Kent Overstreet 2023-11-19 310 closure_type(op, struct data_insert_op, cl);
cafe563591446c Kent Overstreet 2013-03-23 311
60ae81eee86dd7 Slava Pestov 2014-05-22 312 trace_bcache_write(op->c, op->inode, op->bio,
60ae81eee86dd7 Slava Pestov 2014-05-22 313 op->writeback, op->bypass);
220bb38c21b83e Kent Overstreet 2013-09-10 314
220bb38c21b83e Kent Overstreet 2013-09-10 315 bch_keylist_init(&op->insert_keys);
220bb38c21b83e Kent Overstreet 2013-09-10 316 bio_get(op->bio);
b945f655e6185e Kent Overstreet 2023-11-19 317 bch_data_insert_start(&cl->work);
cafe563591446c Kent Overstreet 2013-03-23 318 }
cafe563591446c Kent Overstreet 2013-03-23 319
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-20 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 3:07 [PATCH] closures: CLOSURE_CALLBACK() to fix type punning Kent Overstreet
2023-11-20 7:58 ` kernel test robot
2023-11-20 7:58 ` kernel test robot [this message]
2023-11-29 6:13 ` Coly Li
2023-11-29 20:13 ` Kees Cook
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=202311201549.FNQyD6Xl-lkp@intel.com \
--to=lkp@intel.com \
--cc=colyli@suse.de \
--cc=keescook@chromium.org \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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.