blob: e947f21857a878e71c050c14f71cfcab259ef044 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
|
<think>
Okay, I'm looking at this bug report: "linux-user getsockopt(fd, SOL_SOCKET, SO_ERROR) returns host errno to target." Hmm, let's break it down. The function in question is getsockopt, which is used to get socket options. The parameters are fd (file descriptor), SOL_SOCKET (the level for socket options), and SO_ERROR (specific option to retrieve the error).
So, the issue here is that when getsockopt is called with these parameters, it's returning the host's errno instead of translating it correctly for the target environment. Since this relates to how system calls are handled in user-mode translation, specifically involving sockets, I think this falls under the category related to socket handling.
Looking at the possible categories: device, graphic, socket, network... "socket" seems directly relevant because getsockopt is a socket-level function. It's not about assembly lowering or permissions. The problem isn't with performance or kernel but rather with how socket errors are being reported across environments.
</think>
socket
|