selftests/bpf: Fix namespace usage in flow_dissector tests

The flow_dissector_skb_less_{direct,indirect}_attach tests support parallel
execution, but each tries to create the same namespace and may result in
timing-dependent test failures:

root@qemu-armhf# ./test_progs -j2 -t flow_dissector_skb_less
Cannot create namespace file "/run/netns/flow_dissector_skb_less_indirect_attach_ns": File exists
Cannot open network namespace "flow_dissector_skb_less_indirect_attach_ns": No such file or directory
test_flow_dissector_skb_less_direct_attach:FAIL:create and open netns unexpected error: -2
torvalds#116     flow_dissector_skb_less_direct_attach:FAIL
test_flow_dissector_skb_less_indirect_attach:FAIL:create and open netns unexpected error: -2
torvalds#117     flow_dissector_skb_less_indirect_attach:FAIL

Fix the apparent typo, allowing each test use of a unique net namespace and
avoiding these errors.

Fixes: 2b044dd ("selftests/bpf: re-split main function into dedicated tests")
Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>

Author: guidosarducci

tools/testing/selftests/bpf/prog_tests/flow_dissector.c

@@ -706,7 +706,7 @@ void test_flow_dissector_skb_less_direct_attach(void)
 	struct bpf_flow *skel;
 	struct netns_obj *ns;
 
-	ns = netns_new("flow_dissector_skb_less_indirect_attach_ns", true);
+	ns = netns_new("flow_dissector_skb_less_direct_attach_ns", true);
 	if (!ASSERT_OK_PTR(ns, "create and open netns"))
 		return;