From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfilter: fix CONFIG_NF_REJECT_IPV6=m link error
Date: Mon, 9 Apr 2018 16:37:41 +0200 [thread overview]
Message-ID: <20180409143741.dzooqrzcgi2bnvd5@salvia> (raw)
In-Reply-To: <20180409105322.2247296-1-arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
Hi Arnd,
On Mon, Apr 09, 2018 at 12:53:12PM +0200, Arnd Bergmann wrote:
> We get a new link error with CONFIG_NFT_REJECT_INET=y and CONFIG_NF_REJECT_IPV6=m
I think we can update NFT_REJECT_INET so it depends on NFT_REJECT_IPV4
and NFT_REJECT_IPV6. This doesn't allow here CONFIG_NFT_REJECT_INET=y
and CONFIG_NF_REJECT_IPV6=m.
I mean, just like we do with NFT_FIB_INET.
BTW, I think this problem has been is not related to the recent patch,
but something older that kbuild robot has triggered more easily for
some reason?
Thanks for your patch!
[-- Attachment #2: x.patch --]
[-- Type: text/x-diff, Size: 358 bytes --]
diff --git a/net/netfilter/Kconfig b/net/netfilter/Kconfig
index d3220b43c832..b48c57bb9aaf 100644
--- a/net/netfilter/Kconfig
+++ b/net/netfilter/Kconfig
@@ -601,7 +601,8 @@ config NFT_REJECT
config NFT_REJECT_INET
depends on NF_TABLES_INET
- default NFT_REJECT
+ depends on NFT_REJECT_IPV4
+ depends on NFT_REJECT_IPV6
tristate
config NFT_COMPAT
next prev parent reply other threads:[~2018-04-09 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 10:53 [PATCH] netfilter: fix CONFIG_NF_REJECT_IPV6=m link error Arnd Bergmann
2018-04-09 14:37 ` Pablo Neira Ayuso [this message]
2018-04-09 14:43 ` Arnd Bergmann
2018-04-13 13:15 ` Pablo Neira Ayuso
2018-04-13 14:52 ` Arnd Bergmann
2018-04-14 6:54 ` [PATCH] netfilter: CONFIG_NF_REJECT_IPV{4,6} becomes bool toggle kbuild test robot
2018-04-14 9:45 ` kbuild test robot
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=20180409143741.dzooqrzcgi2bnvd5@salvia \
--to=pablo@netfilter.org \
--cc=arnd@arndb.de \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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