From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Yang Yingliang <yangyingliang@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:openEuler-1.0-LTS 1593/1593] block/bio-integrity.c:41:6: warning: no previous prototype for '__bio_integrity_free'
Date: Fri, 25 Apr 2025 10:03:05 +0800 [thread overview]
Message-ID: <202504250942.HWyvS6HD-lkp@intel.com> (raw)
Hi Chengguang,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head: 08111f03f1ec65598372cfe9bf64f366d575671e
commit: f9c4e7b09f7d51f9256fe51b9c40657cd7302530 [1593/1593] block: release bip in a right way in error path
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20250425/202504250942.HWyvS6HD-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250425/202504250942.HWyvS6HD-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/202504250942.HWyvS6HD-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> block/bio-integrity.c:41:6: warning: no previous prototype for '__bio_integrity_free' [-Wmissing-prototypes]
41 | void __bio_integrity_free(struct bio_set *bs, struct bio_integrity_payload *bip)
| ^~~~~~~~~~~~~~~~~~~~
vim +/__bio_integrity_free +41 block/bio-integrity.c
40
> 41 void __bio_integrity_free(struct bio_set *bs, struct bio_integrity_payload *bip)
42 {
43 if (bs && mempool_initialized(&bs->bio_integrity_pool)) {
44 if (bip->bip_vec)
45 bvec_free(&bs->bvec_integrity_pool, bip->bip_vec,
46 bip->bip_slab);
47 mempool_free(bip, &bs->bio_integrity_pool);
48 } else {
49 kfree(bip);
50 }
51 }
52
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-25 2:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202504250942.HWyvS6HD-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yangyingliang@huawei.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 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.