All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Sasha Levin <sashal@kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [linux-stable-rc:queue/5.4 23/26] crypto/algapi.c:431:3: error: non-void function 'crypto_unregister_alg' should return a value
Date: Sat, 6 May 2023 18:40:41 +0800	[thread overview]
Message-ID: <202305061817.CE4IZ6k3-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git queue/5.4
head:   7e4ab664280ce88c69fad5875e49d02c7c4cf810
commit: 0eda47db82148ff66cd46f5b4677cd98336b1b3f [23/26] crypto: api - Demote BUG_ON() in crypto_unregister_alg() to a WARN_ON()
config: x86_64-randconfig-a012-20230501 (https://download.01.org/0day-ci/archive/20230506/202305061817.CE4IZ6k3-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=0eda47db82148ff66cd46f5b4677cd98336b1b3f
        git remote add linux-stable-rc https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
        git fetch --no-tags linux-stable-rc queue/5.4
        git checkout 0eda47db82148ff66cd46f5b4677cd98336b1b3f
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202305061817.CE4IZ6k3-lkp@intel.com/

All errors (new ones prefixed by >>):

>> crypto/algapi.c:431:3: error: non-void function 'crypto_unregister_alg' should return a value [-Wreturn-type]
                   return;
                   ^
   1 error generated.


vim +/crypto_unregister_alg +431 crypto/algapi.c

   417	
   418	int crypto_unregister_alg(struct crypto_alg *alg)
   419	{
   420		int ret;
   421		LIST_HEAD(list);
   422	
   423		down_write(&crypto_alg_sem);
   424		ret = crypto_remove_alg(alg, &list);
   425		up_write(&crypto_alg_sem);
   426	
   427		if (ret)
   428			return ret;
   429	
   430		if (WARN_ON(refcount_read(&alg->cra_refcnt) != 1))
 > 431			return;
   432	
   433		if (alg->cra_destroy)
   434			alg->cra_destroy(alg);
   435	
   436		crypto_remove_final(&list);
   437		return 0;
   438	}
   439	EXPORT_SYMBOL_GPL(crypto_unregister_alg);
   440	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests

                 reply	other threads:[~2023-05-06 10:41 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=202305061817.CE4IZ6k3-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=toke@redhat.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.