From: Khem Raj <raj.khem@gmail.com>
To: fstests@vger.kernel.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: [PATCH 2/2] Add missing STATX_ATTR_* defines from musl sys/stat.h
Date: Mon, 25 Mar 2024 10:53:23 -0700 [thread overview]
Message-ID: <20240325175323.3450750-2-raj.khem@gmail.com> (raw)
In-Reply-To: <20240325175323.3450750-1-raj.khem@gmail.com>
These defines are not provided by sys/stat.h on musl but are
in glibc's sys/stat.h, therefore to compile the tests on musl
based systems add the missing defines from linux/stat.h
if they are not provided
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
src/statx.h | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/src/statx.h b/src/statx.h
index 3f239d79..12599f5b 100644
--- a/src/statx.h
+++ b/src/statx.h
@@ -12,6 +12,18 @@
#define AT_STATX_DONT_SYNC 0x4000 /* - Don't sync attributes with the server */
#endif
+#ifndef STATX_ATTR_COMPRESSED
+#define STATX_ATTR_COMPRESSED 0x00000004 /* [I] File is compressed by the fs */
+#define STATX_ATTR_IMMUTABLE 0x00000010 /* [I] File is marked immutable */
+#define STATX_ATTR_APPEND 0x00000020 /* [I] File is append-only */
+#define STATX_ATTR_NODUMP 0x00000040 /* [I] File is not to be dumped */
+#define STATX_ATTR_ENCRYPTED 0x00000800 /* [I] File requires key to decrypt in fs */
+#define STATX_ATTR_AUTOMOUNT 0x00001000 /* Dir: Automount trigger */
+#define STATX_ATTR_MOUNT_ROOT 0x00002000 /* Root of a mount */
+#define STATX_ATTR_VERITY 0x00100000 /* [I] Verity protected file */
+#define STATX_ATTR_DAX 0x00200000 /* File is currently in DAX state */
+#endif
+
#ifndef AT_NO_AUTOMOUNT
#define AT_NO_AUTOMOUNT 0x800 /* Suppress terminal automount traversal */
#endif
--
2.44.0
next prev parent reply other threads:[~2024-03-25 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 17:53 [PATCH 1/2] include libgen.h for basename API prototype Khem Raj
2024-03-25 17:53 ` Khem Raj [this message]
2024-03-26 0:20 ` Darrick J. Wong
2024-03-26 1:23 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240325175323.3450750-2-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=fstests@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.