From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: dccp@vger.kernel.org
Subject: [PATCH 3/4][TCP]: syn_flood_warning is only needed if CONFIG_SYN_COOKIES is selected
Date: Wed, 04 Jan 2006 04:13:09 +0000 [thread overview]
Message-ID: <39e6f6c70601032013m36fa395age319ce53976dedd8@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 139 bytes --]
Hi David,
Please consider pulling from:
master.kernel.org:/pub/scm/linux/kernel/git/acme/net-2.6.git
Best Regards,
- Arnaldo
[-- Attachment #2: 3.patch --]
[-- Type: text/x-patch, Size: 1269 bytes --]
tree 31a9a37e00b690edf3e54d61393e364f203549c3
parent e4dfd449c80a41bb615b23d0fc198ba08360a1f8
author Arnaldo Carvalho de Melo <acme@mandriva.com> 1136347086 -0200
committer Arnaldo Carvalho de Melo <acme@mandriva.com> 1136347086 -0200
[TCP]: syn_flood_warning is only needed if CONFIG_SYN_COOKIES is selected
CC net/ipv4/tcp_ipv4.o
/pub/scm/linux/kernel/git/acme/net-2.6/net/ipv4/tcp_ipv4.c:665: warning:
'syn_flood_warning' defined but not used
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
------------------------------------------------------------------------------
tcp_ipv4.c | 2 ++
1 file changed, 2 insertions(+)
------------------------------------------------------------------------------
diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
index 5c70493..e9f83e5 100644
--- a/net/ipv4/tcp_ipv4.c
+++ b/net/ipv4/tcp_ipv4.c
@@ -661,6 +661,7 @@ static void tcp_v4_reqsk_destructor(stru
kfree(inet_rsk(req)->opt);
}
+#ifdef CONFIG_SYN_COOKIES
static void syn_flood_warning(struct sk_buff *skb)
{
static unsigned long warntime;
@@ -672,6 +673,7 @@ static void syn_flood_warning(struct sk_
ntohs(skb->h.th->dest));
}
}
+#endif
/*
* Save and compile IPv4 options into the request_sock if needed.
reply other threads:[~2006-01-04 4:13 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=39e6f6c70601032013m36fa395age319ce53976dedd8@mail.gmail.com \
--to=acme@ghostprotocols.net \
--cc=dccp@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