From: kernel test robot <lkp@intel.com>
To: "Jose M. Guisado Gomez" <guigom@riseup.net>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [linux-next:master 2072/5794] ERROR: modpost: "nf_reject_skb_v4_tcp_reset" undefined!
Date: Mon, 16 Nov 2020 09:14:39 +0800 [thread overview]
Message-ID: <202011160935.pT8mj7qy-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 92edc4aef86780a8ad01b092c6d6630bb3cb423d
commit: fa538f7cf05aab61cd91e01c160d4a09c81b8ffe [2072/5794] netfilter: nf_reject: add reject skbuff creation helpers
config: i386-randconfig-a005-20201116 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=fa538f7cf05aab61cd91e01c160d4a09c81b8ffe
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout fa538f7cf05aab61cd91e01c160d4a09c81b8ffe
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "nf_reject_skb_v4_tcp_reset" [net/bridge/netfilter/nft_reject_bridge.ko] undefined!
>> ERROR: modpost: "nf_reject_skb_v4_unreach" [net/bridge/netfilter/nft_reject_bridge.ko] undefined!
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37951 bytes --]
reply other threads:[~2020-11-16 1:15 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=202011160935.pT8mj7qy-lkp@intel.com \
--to=lkp@intel.com \
--cc=guigom@riseup.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=pablo@netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).