From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: fw@strlen.de, eric.dumazet@gmail.com, davem@davemloft.net,
netdev@vger.kernel.org
Subject: [PATCH net-next,RFC 7/8] net: ipv4: place cb handling away from fragment transformer
Date: Wed, 3 Apr 2019 17:40:00 +0200 [thread overview]
Message-ID: <20190403154001.8177-8-pablo@netfilter.org> (raw)
In-Reply-To: <20190403154001.8177-1-pablo@netfilter.org>
Deal with the IPCB() area away from the fragment transformer.
The bridge codebase has its own control buffer layout, move specific IP
control buffer into function.
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---
net/ipv4/ip_output.c | 34 ++++++++++++++++++++++------------
1 file changed, 22 insertions(+), 12 deletions(-)
diff --git a/net/ipv4/ip_output.c b/net/ipv4/ip_output.c
index 1dc731d7be0e..bb0a13f78b43 100644
--- a/net/ipv4/ip_output.c
+++ b/net/ipv4/ip_output.c
@@ -635,6 +635,25 @@ void ip_frag_init(struct sk_buff *skb, unsigned int hlen,
}
EXPORT_SYMBOL(ip_frag_init);
+static void ip_frag_ipcb(struct sk_buff *from, struct sk_buff *to,
+ bool first_frag, struct ip_frag_state *state)
+{
+ /* Copy the flags to each fragment. */
+ IPCB(to)->flags = IPCB(from)->flags;
+
+ if (IPCB(from)->flags & IPSKB_FRAG_PMTU)
+ state->iph->frag_off |= htons(IP_DF);
+
+ /* ANK: dirty, but effective trick. Upgrade options only if
+ * the segment to be fragmented was THE FIRST (otherwise,
+ * options are already fixed) and make it ONCE
+ * on the initial skb, so that all the following fragments
+ * will inherit fixed options.
+ */
+ if (first_frag)
+ ip_options_fragment(from);
+}
+
struct sk_buff *ip_frag_next(struct sk_buff *skb, struct ip_frag_state *state)
{
unsigned int len = state->left;
@@ -693,18 +712,6 @@ struct sk_buff *ip_frag_next(struct sk_buff *skb, struct ip_frag_state *state)
iph = ip_hdr(skb2);
iph->frag_off = htons((state->offset >> 3));
- if (IPCB(skb)->flags & IPSKB_FRAG_PMTU)
- iph->frag_off |= htons(IP_DF);
-
- /* ANK: dirty, but effective trick. Upgrade options only if
- * the segment to be fragmented was THE FIRST (otherwise,
- * options are already fixed) and make it ONCE
- * on the initial skb, so that all the following fragments
- * will inherit fixed options.
- */
- if (state->offset == 0)
- ip_options_fragment(skb);
-
/*
* Added AC : If we are fragmenting a fragment that's not the
* last fragment then keep MF on each bit
@@ -854,11 +861,14 @@ int ip_do_fragment(struct net *net, struct sock *sk, struct sk_buff *skb,
*/
while (state.left > 0) {
+ bool first_frag = (state.offset == 0);
+
skb2 = ip_frag_next(skb, &state);
if (IS_ERR(skb2)) {
err = PTR_ERR(skb2);
goto fail;
}
+ ip_frag_ipcb(skb, skb2, first_frag, &state);
/*
* Put this fragment into the sending queue.
--
2.11.0
next prev parent reply other threads:[~2019-04-03 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 15:39 [PATCH net-next,RFC 0/8] connection tracking support for bridge Pablo Neira Ayuso
2019-04-03 15:39 ` [PATCH net-next,RFC 1/8] net: use kfree_skb_list() from ip_do_fragment() Pablo Neira Ayuso
2019-04-04 10:13 ` Florian Westphal
2019-04-03 15:39 ` [PATCH net-next,RFC 2/8] net: ipv4: add skbuff fraglist split iterator Pablo Neira Ayuso
2019-04-03 15:39 ` [PATCH net-next,RFC 3/8] net: ipv6: " Pablo Neira Ayuso
2019-04-03 15:39 ` [PATCH net-next,RFC 4/8] net: ipv4: split skbuff into fragments transformer Pablo Neira Ayuso
2019-04-03 15:39 ` [PATCH net-next,RFC 5/8] net: ipv6: " Pablo Neira Ayuso
2019-04-03 15:39 ` [PATCH net-next,RFC 6/8] net: ipv4: place cb handling away from fraglist iterator Pablo Neira Ayuso
2019-04-03 15:40 ` Pablo Neira Ayuso [this message]
2019-04-03 15:40 ` [PATCH net-next,RFC 8/8] netfilter: bridge: add basic conntrack support Pablo Neira Ayuso
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=20190403154001.8177-8-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--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;
as well as URLs for NNTP newsgroup(s).