Add tls cleanup to protect tcp

[Meissi-jian]

Summary

This PR addresses an issue where abnormal application exits were causing crash in the TCP/IP stack due to tcp conn will be used after free.

Impact

tcp_send / tcp_recv / tcp_connect
Impact on user: YES (Applications using TCP will now have improved stability on abnormal exit).
Impact on build: NO
Impact on hardware: NO
Impact on documentation: YES (Documentation should be updated to describe the new TLS cleanup mechanism and how it prevents issues on application exit)
Impact on security: Potentially YES (If the abnormal exit was exploitable, this fix might improve security. Explain clearly).
Impact on compatibility: NO (If this is true, state it explicitly)

Testing

Target: sim and others product by monkey
Log: see " pthread is being canceled, need to cleanup cb",and device didn't crash

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR description does not meet the NuttX requirements. It's far too brief and lacks critical information. Here's why and how it can be improved:

Summary:

• Insufficient Detail: "Due to abnormal application exit, so add tls cleanup to protect" is vague. What abnormal application exit? What kind of issues did it cause? Which TLS cleanup is being added? How does this cleanup prevent the issue? Be specific.
• Missing Context: Which functional part of the code is affected (networking, memory management, etc.)?

Impact:

• Too Brief: Just saying "tcp" isn't enough. Explain how TCP is impacted. Does this change affect TCP performance? Does it fix a bug related to TCP connections closing? Answer all the impact questions explicitly (YES/NO and explanation). For example:
  • Impact on user: YES (Applications using TCP will now have improved stability on abnormal exit and potentially prevent resource leaks).
  • Impact on build: NO
  • Impact on hardware: NO
  • Impact on documentation: YES (Documentation should be updated to describe the new TLS cleanup mechanism and how it prevents issues on application exit)
  • Impact on security: Potentially YES (If the abnormal exit was exploitable, this fix might improve security. Explain clearly).
  • Impact on compatibility: NO (If this is true, state it explicitly)

Testing:

• Insufficient Information: "tested passed on product by monkey-test" is not adequate. Provide specifics:
  • Build Host: e.g., Linux (Ubuntu 20.04), x86_64, GCC 9.4.0
  • Target: e.g., sim:qemu-arm
• Missing Logs: The template requests "Testing logs before change" and "Testing logs after change." These are essential for demonstrating that the change addresses the intended issue and doesn't introduce regressions. Include relevant log snippets (even if short) that show the problem before and the improvement after the change. Even a simple demonstration of a crash before and successful operation after would be much better than nothing.

Example of an Improved Summary:

"This PR addresses an issue where abnormal application exits were causing resource leaks and potential instability in the TCP/IP stack due to incomplete TLS cleanup. The change adds a new cleanup function in the net/tcp directory that is called during application exit to ensure all TLS resources are properly released. This prevents memory leaks and potential socket issues in subsequent TCP connections. Fixes #[NuttX Issue Number]."

By providing more specific information and following the template closely, the PR review process will be much more efficient. Reviewers will have the context they need to understand the change and its implications.