From: "Paul E. McKenney" <paulmck@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [paulmck-rcu:dev.2023.02.03a] BUILD REGRESSION c722c164d799860f1a31c82e001221df13dccede
Date: Sat, 4 Feb 2023 18:49:59 -0800 [thread overview]
Message-ID: <20230205024959.GG2948950@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <63df11f7.YArGrbpGISJDiQF3%lkp@intel.com>
On Sun, Feb 05, 2023 at 10:18:31AM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2023.02.03a
> branch HEAD: c722c164d799860f1a31c82e001221df13dccede locktorture: With nested locks, occasionally skip main lock
>
> Error/Warning reports:
>
> https://lore.kernel.org/oe-kbuild-all/202302021723.ucm8d559-lkp@intel.com
> https://lore.kernel.org/oe-kbuild-all/202302021724.SF7KLCrw-lkp@intel.com
>
> Error/Warning: (recently discovered and may have been fixed)
>
> arch/loongarch/kernel/process.c:67:1: warning: 'noreturn' function does return
> arch/powerpc/kernel/smp.c:1768:1: warning: function declared 'noreturn' should not return [-Winvalid-noreturn]
> net/netfilter/ipvs/ip_vs_est.c:552:15: error: too few arguments provided to function-like macro invocation
> net/netfilter/ipvs/ip_vs_est.c:552:17: error: 'kfree_rcu' undeclared (first use in this function); did you mean 'kfree_skb'?
> net/netfilter/ipvs/ip_vs_est.c:552:29: error: macro "kfree_rcu" requires 2 arguments, but only 1 given
> net/netfilter/ipvs/ip_vs_est.c:552:3: error: use of undeclared identifier 'kfree_rcu'; did you mean 'kfree_skb'?
These are due to a patch that has been handed off to its maintainer,
and should be fixed once that is in place.
As always, thank you for your testing efforts!
Thanx, Paul
> Error/Warning ids grouped by kconfigs:
>
> gcc_recent_errors
> |-- loongarch-buildonly-randconfig-r002-20230204
> | `-- arch-loongarch-kernel-process.c:warning:noreturn-function-does-return
> |-- m68k-randconfig-r002-20230205
> | |-- net-netfilter-ipvs-ip_vs_est.c:error:kfree_rcu-undeclared-(first-use-in-this-function)
> | `-- net-netfilter-ipvs-ip_vs_est.c:error:macro-kfree_rcu-requires-arguments-but-only-given
> `-- sparc-allyesconfig
> |-- net-netfilter-ipvs-ip_vs_est.c:error:kfree_rcu-undeclared-(first-use-in-this-function)
> `-- net-netfilter-ipvs-ip_vs_est.c:error:macro-kfree_rcu-requires-arguments-but-only-given
> clang_recent_errors
> |-- powerpc-randconfig-r003-20230204
> | `-- arch-powerpc-kernel-smp.c:warning:function-declared-noreturn-should-not-return
> |-- powerpc-randconfig-r033-20230204
> | `-- arch-powerpc-kernel-smp.c:warning:function-declared-noreturn-should-not-return
> `-- s390-randconfig-r044-20230205
> |-- net-netfilter-ipvs-ip_vs_est.c:error:too-few-arguments-provided-to-function-like-macro-invocation
> `-- net-netfilter-ipvs-ip_vs_est.c:error:use-of-undeclared-identifier-kfree_rcu
>
> elapsed time: 1560m
>
> configs tested: 66
> configs skipped: 2
>
> gcc tested configs:
> x86_64 allnoconfig
> arc defconfig
> s390 allmodconfig
> alpha defconfig
> um i386_defconfig
> s390 defconfig
> um x86_64_defconfig
> s390 allyesconfig
> powerpc allnoconfig
> ia64 allmodconfig
> x86_64 randconfig-a004
> x86_64 randconfig-a002
> x86_64 randconfig-a006
> sh allmodconfig
> mips allyesconfig
> powerpc allmodconfig
> m68k allmodconfig
> alpha allyesconfig
> m68k allyesconfig
> arc allyesconfig
> x86_64 rhel-8.3-syz
> x86_64 rhel-8.3-kunit
> x86_64 rhel-8.3-kvm
> x86_64 rhel-8.3-bpf
> arc randconfig-r043-20230204
> s390 randconfig-r044-20230204
> riscv randconfig-r042-20230204
> x86_64 defconfig
> x86_64 rhel-8.3
> x86_64 allyesconfig
> x86_64 rhel-8.3-kselftests
> x86_64 rhel-8.3-func
> x86_64 randconfig-a013
> i386 randconfig-a001
> x86_64 randconfig-a011
> i386 randconfig-a003
> x86_64 randconfig-a015
> i386 randconfig-a005
> i386 defconfig
> i386 allyesconfig
> i386 randconfig-a014
> i386 randconfig-a012
> i386 randconfig-a016
> arc randconfig-r043-20230205
> arm randconfig-r046-20230205
> arm defconfig
>
> clang tested configs:
> x86_64 randconfig-a001
> x86_64 randconfig-a003
> x86_64 randconfig-a005
> hexagon randconfig-r041-20230204
> arm randconfig-r046-20230204
> hexagon randconfig-r045-20230204
> x86_64 rhel-8.3-rust
> x86_64 randconfig-a014
> x86_64 randconfig-a012
> i386 randconfig-a002
> i386 randconfig-a004
> x86_64 randconfig-a016
> i386 randconfig-a006
> i386 randconfig-a013
> i386 randconfig-a011
> i386 randconfig-a015
> hexagon randconfig-r045-20230205
> hexagon randconfig-r041-20230205
> riscv randconfig-r042-20230205
> s390 randconfig-r044-20230205
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests
prev parent reply other threads:[~2023-02-05 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 2:18 kernel test robot
2023-02-05 2:49 ` Paul E. McKenney [this message]
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=20230205024959.GG2948950@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®