[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231007180218.231638-1-izbyshev@ispras.ru>
Date: Sat, 7 Oct 2023 21:02:18 +0300
From: Alexey Izbyshev <izbyshev@...ras.ru>
To: musl@...ts.openwall.com
Subject: [PATCH v2] pass AT_NO_AUTOMOUNT when emulating fstatat via statx
AT_NO_AUTOMOUNT is implied for stat/lstat/fstatat syscalls since Linux
3.1 [1]. However, this is not the case for statx syscall, which defaults
to automounting, so this flag must be passed explicitly when statx is
used to implement stat-like functions.
This change affects only arches which use 32-bit seconds in struct kstat,
as well as out-of-tree/future ports to arches which lack SYS_fstatat.
[1] https://git.kernel.org/torvalds/c/b6c8069d3577481390b3f24a8434ad72a3235594
---
Fixed the wrong statement about affected arches in the commit message.
---
src/stat/fstatat.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/stat/fstatat.c b/src/stat/fstatat.c
index 04506375d897..9eed063b26bc 100644
--- a/src/stat/fstatat.c
+++ b/src/stat/fstatat.c
@@ -36,6 +36,7 @@ static int fstatat_statx(int fd, const char *restrict path, struct stat *restric
{
struct statx stx;
+ flag |= AT_NO_AUTOMOUNT;
int ret = __syscall(SYS_statx, fd, path, flag, 0x7ff, &stx);
if (ret) return ret;
--
2.39.2
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
