From: Woody Suwalski <wsuwalski@gmail.com>
To: Robert Gadsdon <rhgadsdon@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.17-rc5
Date: Mon, 21 Feb 2022 11:11:18 -0500 [thread overview]
Message-ID: <013de68c-a30c-6c13-ee08-2af65d5cb849@gmail.com> (raw)
In-Reply-To: <2d30205a-fc22-02e1-5c4b-99b91493580c@gmail.com>
Robert Gadsdon wrote:
> Compile fail. Fedora 35, GCC 11.2.1, x86_64..
>
> ....................
> AR net/netfilter/built-in.a
> LD [M] net/netfilter/nf_conntrack.o
> CC [M] net/netfilter/xt_socket.o
> net/netfilter/xt_socket.c: In function ‘socket_mt_destroy’:
> net/netfilter/xt_socket.c:224:17: error: implicit declaration of
> function ‘nf_defrag_ipv6_disable’; did you mean
> ‘nf_defrag_ipv4_disable’? [-Werror=implicit-function-declaration]
> 224 | nf_defrag_ipv6_disable(par->net);
> | ^~~~~~~~~~~~~~~~~~~~~~
> | nf_defrag_ipv4_disable
> cc1: some warnings being treated as errors
> make[2]: *** [scripts/Makefile.build:288: net/netfilter/xt_socket.o]
> Error 1
> make[1]: *** [scripts/Makefile.build:550: net/netfilter] Error 2
> make: *** [Makefile:1831: net] Error 2
>
>
> - already reported on Feb 11th, at:
> http://lkml.iu.edu/hypermail/linux/kernel/2202.1/05890.html
>
> Robert Gadsdon
> February 20th 2022.
>
Compile failed for me as well.
The workaround:
nf_defrag_ipv6.patch
--- a/net/netfilter/xt_socket.c 2022-02-21 07:29:21.938263397 -0500
+++ b/net/netfilter/xt_socket.c 2022-02-21 07:40:16.730022272 -0500
@@ -17,11 +17,11 @@
#include <net/inet_sock.h>
#include <net/netfilter/ipv4/nf_defrag_ipv4.h>
-#if IS_ENABLED(CONFIG_IP6_NF_IPTABLES)
+//#if IS_ENABLED(CONFIG_IP6_NF_IPTABLES)
#include <linux/netfilter_ipv6/ip6_tables.h>
#include <net/inet6_hashtables.h>
#include <net/netfilter/ipv6/nf_defrag_ipv6.h>
-#endif
+//#endif
#include <net/netfilter/nf_socket.h>
#include <linux/netfilter/xt_socket.h>
Or force use CONFIG_IP6_NF_IPTABLES
Thanks, Woody
next prev parent reply other threads:[~2022-02-21 16:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 21:19 Linux 5.17-rc5 Linus Torvalds
2022-02-20 23:37 ` Robert Gadsdon
2022-02-21 16:11 ` Woody Suwalski [this message]
2022-02-21 14:23 ` Woody Suwalski
2022-02-21 17:56 ` Linus Torvalds
2022-02-21 18:01 ` Eric Dumazet
2022-02-21 18:07 ` Linus Torvalds
2022-02-21 18:21 ` Eric Dumazet
2022-02-21 18:25 ` Pablo Neira Ayuso
2022-02-21 18:28 ` Eric Dumazet
2022-02-21 18:42 ` Pablo Neira Ayuso
2022-02-21 18:22 ` Woody Suwalski
2022-02-21 18:25 ` Pablo Neira Ayuso
2022-02-21 19:52 ` Robert Gadsdon
-- strict thread matches above, loose matches on Subject: below --
2022-02-21 17:44 Linus Torvalds
2022-02-21 18:10 ` Guenter Roeck
2022-02-21 18:31 ` Linus Torvalds
2022-02-21 20:44 ` Guenter Roeck
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=013de68c-a30c-6c13-ee08-2af65d5cb849@gmail.com \
--to=wsuwalski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rhgadsdon@gmail.com \
--cc=torvalds@linux-foundation.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