fix ut_test_md

Signed-off-by: sweeywu <sweetwx6@gmail.com>

Author: wxnzb

docs/proposal/ut_test.md

@@ -77,10 +77,13 @@ change are understandable. This may include API specs (though not always
 required) or even code snippets. If there's any ambiguity about HOW your
 proposal will be implemented, this is the place to discuss them.
 -->
-###  sendmsg.c
+
+### sendmsg.c
 ### mount and set up
 #### mount
+
 - include the sockhash map in workload_sendmsg.c
+
 ```c
 struct {
     __uint(type, BPF_MAP_TYPE_SOCKHASH);
@@ -90,8 +93,10 @@ struct {
     __uint(map_flags, 0);
 } map_of_kmesh_socket SEC(".maps");
 ```
+
 - in workload_test.go
 - load the eBPF program into the kernel
+
 ```go
    //load the eBPF program
  	spec := loadAndPrepSpec(t, path.Join(*testPath, objFilePath))
@@ -103,7 +108,9 @@ struct {
 	// Load the eBPF collection into the kernel
 	coll, err = ebpf.NewCollection(spec)
 ```
+
 - Lookup the sockhash map and attach the sk_msg eBPF program to the map
+
 ```go
     sockMap := coll.Maps["km_socket"]
     t.Log(sockMap.Type())
@@ -115,7 +122,9 @@ struct {
 							Program: prog,
 						})
 ```
+
 #### set up
+
 - Establish a network connection, obtain the file descriptor (fd), insert the fd into the map, and sending messages through this fd will trigger the eBPF program
 ```go
     localIP := get_local_ipv4(t)
@@ -164,6 +173,7 @@ struct {
         t.Logf("Update successful for key: %+v, fd: %d", tupleKey, fd32)
     }
 ```
+
 ### test
 
 - For the sendmsg program, there are key steps:
@@ -177,15 +187,19 @@ struct {
 - The current plan is to write a test that directly verifies whether TLV is written into the message header.
 - Validation method: Check whether TLV is correctly written into the message header.
 - Validation method
+
 ```go
     buf := make([]byte, 64)
     n, _ := ln.Accept().Read(buf)
     t.Logf("Received data: %x", buf[:n])
 ```
+
 ### cgroup_sock.c
 ### mount and set up
 #### mount
+
 - in workload_test.go
+
 ```go
    // mount cgroup2
     mount_cgroup2(t, cgroupPath)
@@ -195,21 +209,26 @@ struct {
     defer coll.Close()
     defer lk.Close()
 ```
+
 #### set up
+
 ```go
 conn, err := net.Dial("tcp4", "...") 
 if err != nil {
     t.Fatalf("Dial failed: %v", err)
 }
 defer conn.Close()
 ```
+
 ### test
+
 - Currently, connect4 and connect6 each have 5 test points.
 - 1
 - handle_kmesh_manage_process(&kmesh_ctx) internally calls bpf_map_update_elem(&map_of_manager, &key, &value, BPF_ANY); or err = bpf_map_delete_elem(&map_of_manager, &key); for verification.
 - When the destination address is CONTROL_CMD_IP: ENABLE_KMESH_PORT, it adds its netns_cookie to the map; when the destination address is CONTROL_CMD_IP: DISABLE_KMESH_PORT, it deletes its netns_cookie from the map.
 - Validation method:
 - Verify the addition when inserting.
+
 ```go
     kmManageMap := coll.Maps["km_manage"]
     if kmManageMap == nil {
@@ -236,7 +255,9 @@ defer conn.Close()
         t.Fatalf("Expected 1 entry in km_manage map, but got %d", count)
     }
 ```
+
 - Validation when deleting
+
 ```go
     iter = kmManageMap.Iterate()
     count = 0
@@ -251,12 +272,14 @@ defer conn.Close()
         t.Fatalf("Expected 0 entry in km_manage map, but got %d", count)
     }
 ```
+
 - Notes
 - Here it may be necessary to mock storage = bpf_sk_storage_get(&map_of_sock_storage, sk, 0, BPF_LOCAL_STORAGE_GET_F_CREATE); inside workload_cgroup_sock_test.c.
 - 2
 - The function sock_traffic_control(&kmesh_ctx) is critical and internally includes
 - frontend_v = map_lookup_frontend(&frontend_k); Consider how to return frontend_v; this must return a value.
 - By constructing a key-value pair so that the map contains this k-v, it can be found; construct the frontend map.
+
 ```go
     //frontend map
     type ip_addr struct {
@@ -286,11 +309,13 @@ defer conn.Close()
         log.Fatalf("Update failed: %v", err)
     }
 ```
+
 - frontend_manager(kmesh_ctx, frontend_v); internally includes
 - kmesh_map_lookup_elem(&map_of_service, key)
 - 2.1: can find:
 - 2.1.1:
 - Test point: waypoint == true in service_value
+
 ```go
 type service_value struct {
     PrioEndpointCount [7]uint32
@@ -307,18 +332,22 @@ s_val := service_value{
     WaypointPort: 55555,                    //Build 
 }
 ```
+
 - At this point, you need to monitor the forwarded address so that the forwarded connection will not be rejected
 
 ### Alternatives
+
 ```go
 test:=localIp+":"+strconv.Itoa(htons(55555))
 -  _, err = net.Listen("tcp4", "10.30.0.124:985")
 ```	
+
 - 2.2.2:
 - 2.2: If not found, perform kmesh_map_lookup_elem(&map_of_backend, key); this must return a value
 - 2.2.1:
 - Test point: waypoint == true in backend_value
 - Construction:
+
 ```go
 type backend_value struct {
     Addr         ip_addr
@@ -342,14 +371,18 @@ if err := BackendMap.Update(&b_key, &b_val, ebpf.UpdateAny); err != nil {
     log.Fatalf("Update failed: %v", err)
 }
 ```
+
 - This traffic is also forwarded, so the forwarded address must be listened to in advance.
+
 ```go
 testIpPort := localIP + ":" + strconv.Itoa(htons(testPort))
 _, err = net.Listen("tcp4", testIpPort)
 ```
+
 - 2.2.2
 - Test point: waypoint == false in backend_value
 - Construction:
+
 ```go
 type backend_value struct {
     Addr         ip_addr
@@ -369,7 +402,9 @@ if err := BackendMap.Update(&b_key, &b_val, ebpf.UpdateAny); err != nil {
     log.Fatalf("Update failed: %v", err)
 }
 ```
+
 - Note: The UpstreamID in the constructed value must match the key length used later when populating km_backend or the key length used in km_service. For example:
+
 ```go
 type backend_key struct {
     BackendUID uint32
@@ -387,7 +422,9 @@ s_key := service_key{
     ServiceID: 1,
 }
 ```
+
 - Validation method:
+
 ```go
 expectedIP := localIP
     expectedPort := strconv.Itoa(htons(testPort))
@@ -396,16 +433,18 @@ expectedIP := localIP
         t.Fatalf("Expected redirected to %s:%s, but got %s:%s", expectedIP, expectedPort, host, port)
     }
 ```
+
 ### cgroup_skb.c
+
 - It is a type supported by bpf_prog_run and can be tested using the first framework.
 - Since it uses the same __sk_buff parameters as tc triggers, it can be written by following that example.
+
 ```c
 #include "ut_common.h"
 #include <linux/bpf.h>
 #include <linux/if_ether.h>
 #include <linux/in.h>
 #include <netinet/tcp.h>
-
 #include "workload/cgroup_skb.c" 
 struct tcp_probe_info mock_info;
 bool mock_ringbuf_called = false;
@@ -504,6 +543,7 @@ int test_ingress_check(struct __sk_buff *ctx)
     test_finish();
 }
 ```
+
 <!--
 What other approaches did you consider, and why did you rule them out? These do
 not need to be as detailed as the proposal, but should include enough