linux-user: Use getcwd syscall directly
The glibc getcwd function returns different errors than the getcwd syscall, which triggers an assertion failure in the glibc getcwd function when running under the emulation. When the syscall returns ENAMETOOLONG, the glibc wrapper uses a fallback implementation that potentially handles an unlimited path length, and returns with ERANGE if the provided buffer is too small. The qemu emulation cannot distinguish the two cases, and thus always returns ERANGE. This is unexpected by the glibc wrapper. Signed-off-by: Andreas Schwab <schwab@suse.de> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Message-Id: <mvmmu3qplvi.fsf@suse.de> [lv: updated description] Signed-off-by: Laurent Vivier <laurent@vivier.eu>
This commit is contained in:
parent
4d213001b3
commit
0f6bb1958f
@ -388,14 +388,7 @@ static bitmask_transtbl fcntl_flags_tbl[] = {
|
||||
{ 0, 0, 0, 0 }
|
||||
};
|
||||
|
||||
static int sys_getcwd1(char *buf, size_t size)
|
||||
{
|
||||
if (getcwd(buf, size) == NULL) {
|
||||
/* getcwd() sets errno */
|
||||
return (-1);
|
||||
}
|
||||
return strlen(buf)+1;
|
||||
}
|
||||
_syscall2(int, sys_getcwd1, char *, buf, size_t, size)
|
||||
|
||||
#ifdef TARGET_NR_utimensat
|
||||
#if defined(__NR_utimensat)
|
||||
|
Loading…
Reference in New Issue
Block a user