SockSend: remove extraneous msg_controllen assignment + micro nit fixups.

My understanding is that:
CMSG_SPACE macro accounts for the possible trailing padding in the case
of multiple ancillary messages (cmsghdr + cmsg_data) within the same msghdr.
And msghdr.msg_controllen is the sum of individual iteration step sizes -
i.e. sum of CMSG_SPACE of each contained ancillary message.

To clarify, as the current code is only sending a single ancillary message,
the "wrong" length given to the outer msg_controllen is fine in practice,
but I think it's still cleaner to use the correct (general case) macro.

Extra refs:
* kernel macros:
  https://elixir.bootlin.com/linux/v4.19/source/include/linux/socket.h#L97
* ascii diagram from elsewhere in the kernel:
  https://elixir.bootlin.com/linux/v4.19/source/net/sctp/socket.c#L8082

Change-Id: I8c66d8cb7b412e4b53fe83b41ca7bba9b341d739
1 file changed
tree: 92fd2b6a9d51447baef268bff9b3b2c103993601
  1. build_overrides/
  2. buildtools/
  3. debian/
  4. docs/
  5. gn/
  6. include/
  7. infra/
  8. protos/
  9. src/
  10. test/
  11. tools/
  12. ui/
  13. .clang-format
  14. .gitignore
  15. .gn
  16. .travis.yml
  17. Android.bp
  18. Android.bp.extras
  19. BUILD.gn
  20. codereview.settings
  21. heapprofd.rc
  22. MODULE_LICENSE_APACHE2
  23. NOTICE
  24. OWNERS
  25. perfetto.rc
  26. PRESUBMIT.py
  27. README.chromium
  28. README.md
README.md

Perfetto - Performance instrumentation and tracing

Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.

See www.perfetto.dev for docs.

Bugs

  • For bugs affecting Android or the tracing internals use the internal bug tracker (go/perfetto-bugs).
  • For bugs affecting Chrome use http://crbug.com, Component:Speed>Tracing label:Perfetto.