From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: IPv4 NAT doesn't compile in 2.4.4
Date: Sat, 28 Apr 2001 17:25:54 +0100 [thread overview]
Message-ID: <20010428172554.H21792@flint.arm.linux.org.uk> (raw)
net/network.o: In function `init_or_cleanup':
net/network.o(.text+0x4a530): relocation truncated to fit: R_ARM_PC24 ip_nat_cleanup
says it all.
ip_nat_standalone.c:
static int init_or_cleanup(int init)
{
...
cleanup_nat:
ip_nat_cleanup();
...
}
ip_nat_core:
void __exit ip_nat_cleanup(void)
{
ip_ct_selective_cleanup(&clean_nat, NULL);
ip_conntrack_destroyed = NULL;
}
*Don't* do this - its fundamentally wrong. Code in the kernel should _not_
reference code that has been removed by the linker.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next reply other threads:[~2001-04-28 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 16:25 Russell King [this message]
2001-04-28 21:07 ` IPv4 NAT doesn't compile in 2.4.4 David S. Miller
2001-04-28 21:21 ` Russell King
2001-04-28 21:24 ` David S. Miller
2001-05-02 4:57 ` Rusty Russell
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=20010428172554.H21792@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@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