aboutsummaryrefslogtreecommitdiff
path: root/target/hexagon/hex_regs.h
diff options
context:
space:
mode:
authorMichael Tokarev <mjt@tls.msk.ru>2021-09-01 16:16:24 +0300
committerroot <root@tls.msk.ru>2021-09-06 17:18:54 +0300
commit118d527f2e4baec5fe8060b22a6212468b8e4d3f (patch)
treed8f50851ec9a29c535e38abccd2f0f75eb48b37c /target/hexagon/hex_regs.h
parent935efca6c246c108253b0e4e51cc87648fc7ca10 (diff)
qemu-sockets: fix unix socket path copy (again)
Commit 4cfd970ec188558daa6214f26203fe553fb1e01f added an assert which ensures the path within an address of a unix socket returned from the kernel is at least one byte and does not exceed sun_path buffer. Both of this constraints are wrong: A unix socket can be unnamed, in this case the path is completely empty (not even \0) And some implementations (notable linux) can add extra trailing byte (\0) _after_ the sun_path buffer if we passed buffer larger than it (and we do). So remove the assertion (since it causes real-life breakage) but at the same time fix the usage of sun_path. Namely, we should not access sun_path[0] if kernel did not return it at all (this is the case for unnamed sockets), and use the returned salen when copyig actual path as an upper constraint for the amount of bytes to copy - this will ensure we wont exceed the information provided by the kernel, regardless whenever there is a trailing \0 or not. This also helps with unnamed sockets. Note the case of abstract socket, the sun_path is actually a blob and can contain \0 characters, - it should not be passed to g_strndup and the like, it should be accessed by memcpy-like functions. Fixes: 4cfd970ec188558daa6214f26203fe553fb1e01f Fixes: http://bugs.debian.org/993145 Signed-off-by: Michael Tokarev <mjt@tls.msk.ru> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com> CC: qemu-stable@nongnu.org
Diffstat (limited to 'target/hexagon/hex_regs.h')
0 files changed, 0 insertions, 0 deletions