From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Martin Lau <kafai@fb.com>
Cc: "ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH bpf-next] filter: add BPF_ADJ_ROOM_DATA mode to bpf_skb_adjust_room()
Date: Sun, 11 Nov 2018 00:43:27 +0100 [thread overview]
Message-ID: <a2e44e4c-03f3-5c8a-d209-c576da218395@6wind.com> (raw)
In-Reply-To: <20181109185131.7f7osxg2tfp2xapx@kafai-mbp.dhcp.thefacebook.com>
Le 09/11/2018 à 19:51, Martin Lau a écrit :
> On Thu, Nov 08, 2018 at 04:11:37PM +0100, Nicolas Dichtel wrote:
[snip]
>> +static int bpf_skb_data_shrink(struct sk_buff *skb, u32 len)
>> +{
>> + unsigned short hhlen = skb->dev->header_ops ?
>> + skb->dev->hard_header_len : 0;
>> + int ret;
>> +
>> + ret = skb_unclone(skb, GFP_ATOMIC);
>> + if (unlikely(ret < 0))
>> + return ret;
>> +
>> + __skb_pull(skb, len);
>> + skb_reset_mac_header(skb);
>> + skb_reset_network_header(skb);
>> + skb->network_header += hhlen;
>> + skb_reset_transport_header(skb);
> hmm...why transport_header does not need += hhlen here
> while network_header does?
network_header is mandatory because bpf_redirect(BPF_F_INGRESS) can be called
and network_header is expected to be correctly set in this case.
For transport_header, I choose to not set it, because the stack will set it
later (for example ip_rcv_core()).
Regards,
Nicolas
next prev parent reply other threads:[~2018-11-11 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 15:11 [PATCH bpf-next] filter: add BPF_ADJ_ROOM_DATA mode to bpf_skb_adjust_room() Nicolas Dichtel
2018-11-09 18:51 ` Martin Lau
2018-11-10 23:43 ` Nicolas Dichtel [this message]
2018-11-12 18:39 ` Martin Lau
2018-11-13 16:35 ` [PATCH bpf-next v2] " Nicolas Dichtel
2018-11-17 4:52 ` Alexei Starovoitov
2018-11-20 1:06 ` Daniel Borkmann
2018-11-21 14:43 ` Nicolas Dichtel
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=a2e44e4c-03f3-5c8a-d209-c576da218395@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kafai@fb.com \
--cc=netdev@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