Received-SPF: pass (google.com: domain of linux-kernel+bounces-164676-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Message-ID: <13e141a2-ce22-42c8-b462-348ee700fe03@quicinc.com>
Date: Tue, 30 Apr 2024 12:59:31 -0700
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [RFC PATCH bpf-next v5 2/2] net: Add additional bit to support
 clockid_t timestamp type
Content-Language: en-US
To: Martin KaFai Lau <martin.lau@linux.dev>
CC: "David S. Miller" <davem@davemloft.net>,
        Eric Dumazet
	<edumazet@google.com>, Jakub Kicinski <kuba@kernel.org>,
        Paolo Abeni
	<pabeni@redhat.com>, <netdev@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>, Andrew Halaney <ahalaney@redhat.com>,
        "Willem
 de Bruijn" <willemdebruijn.kernel@gmail.com>,
        Martin KaFai Lau
	<martin.lau@kernel.org>,
        Daniel Borkmann <daniel@iogearbox.net>, bpf
	<bpf@vger.kernel.org>,
        <kernel@quicinc.com>
References: <20240424222028.1080134-1-quic_abchauha@quicinc.com>
 <20240424222028.1080134-3-quic_abchauha@quicinc.com>
 <c20eb574-22f4-49f8-a213-5ff57eb6222e@linux.dev>
From: "Abhishek Chauhan (ABC)" <quic_abchauha@quicinc.com>
In-Reply-To: <c20eb574-22f4-49f8-a213-5ff57eb6222e@linux.dev>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit


On 4/26/2024 4:55 PM, Martin KaFai Lau wrote:
> On 4/24/24 3:20 PM, Abhishek Chauhan wrote:
>> diff --git a/net/ipv6/ip6_output.c b/net/ipv6/ip6_output.c
>> index a9e819115622..63e4cc30d18d 100644
>> --- a/net/ipv6/ip6_output.c
>> +++ b/net/ipv6/ip6_output.c
>> @@ -955,7 +955,7 @@ int ip6_fragment(struct net *net, struct sock *sk, struct sk_buff *skb,
>>               if (iter.frag)
>>                   ip6_fraglist_prepare(skb, &iter);
>>   -            skb_set_delivery_time(skb, tstamp, tstamp_type);
>> +            skb_set_tstamp_type_frm_clkid(skb, tstamp, tstamp_type);
>>               err = output(net, sk, skb);
>>               if (!err)
>>                   IP6_INC_STATS(net, ip6_dst_idev(&rt->dst),
>> @@ -1016,7 +1016,7 @@ int ip6_fragment(struct net *net, struct sock *sk, struct sk_buff *skb,
>>           /*
>>            *    Put this fragment into the sending queue.
>>            */
>> -        skb_set_delivery_time(frag, tstamp, tstamp_type);
>> +        skb_set_tstamp_type_frm_clkid(frag, tstamp, tstamp_type);
>>           err = output(net, sk, frag);
>>           if (err)
>>               goto fail;
> 
> When replying another thread and looking closer at the ip6 changes, these two line changes should not be needed.

Similar code exists in ip_output.c for ipv4 packets  =>  ip_do_fragment => I was thinking do we need 
require that code or not. 

Since in both functionality are the same, only difference is protocol. 

From what i see is the for Frag cases in both ipv4 and ipv6, previously skb->tstamp_type was being 
set for each fragments. 

If we are planning to not do it for ip6 the same should follow for ip4 too.