tree b1341d7b5bc444dc899a574a98e5de5064df84f5
parent a6e270392a8c5ee91d5fbecbe6476f39f337d408
author Dmitrii Merkurev <dimorinny@google.com> 1673570434 +0000
committer Dmitrii Merkurev <dimorinny@google.com> 1673998370 +0000

Fix SIGPIPE handling in the socket_vsock_proxy tool

Was able to catch that with some of fastboot clients
(for example default fastboot in the acloud instances)
fastboot connection is unexpectively closed and
the whole proxy process is turned down because of that.

According to strace this problem is causeв by SIGPIPE signal
default behaviour, which according to jemoreira comment on
Proxy must be disabled and handled as a regular write error.

So doing it to fix this particular problem and improve the
stability of adb / fastboot.

Test: checked fastboot proxy is not crashing with the different fastboot clients
Test: checked adb works with --adb_mode=vsock_tunnel
Bug: 265289715

Change-Id: Ic781bf26526393c24e52b72c5cafbe8a2f23e64f
Signed-off-by: Dmitrii Merkurev <dimorinny@google.com>