From: Jan Polensky <japo@linux.ibm.com>
To: chrubis@suse.cz, pvorel@suse.cz
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: [LTP] [PATCH v1 2/3] setxattr02: Adapt test for kernel 7.0+ socket xattr support
Date: Mon, 9 Mar 2026 18:20:56 +0100 [thread overview]
Message-ID: <20260309172057.272946-3-japo@linux.ibm.com> (raw)
In-Reply-To: <20260309172057.272946-1-japo@linux.ibm.com>
Starting with kernel 7.0.0, sockets support extended attributes in the
user.* namespace. This behavior was enabled by dc0876b9846d ("xattr:
support extended attributes on sockets"), which permits user.* xattrs on
S_IFSOCK inodes (previously rejected with -EPERM).
Adapts the test to expect success (exp_err = 0) instead of EPERM when
testing setxattr(2) on sockets with kernel 7.0+.
Signed-off-by: Jan Polensky <japo@linux.ibm.com>
---
testcases/kernel/syscalls/setxattr/setxattr02.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/testcases/kernel/syscalls/setxattr/setxattr02.c b/testcases/kernel/syscalls/setxattr/setxattr02.c
index 9f5f998da9ba..ac2ad8678d31 100644
--- a/testcases/kernel/syscalls/setxattr/setxattr02.c
+++ b/testcases/kernel/syscalls/setxattr/setxattr02.c
@@ -132,6 +132,10 @@ static void verify_setxattr(unsigned int i)
if (TST_RET == -1 && TST_ERR == EOPNOTSUPP)
tst_brk(TCONF, "setxattr(2) not supported");
+ /* consider newer kernels */
+ if ((tst_kvercmp(7, 0, 0) >= 0) && (strncmp(tc[i].fname, SOCK, strlen(SOCK)) == 0))
+ tc[i].exp_err = 0;
+
/* success */
if (!tc[i].exp_err) {
--
2.53.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-09 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 17:20 [LTP] [PATCH v1 0/3] LTP: adjust socket xattr tests for kernel 7.0+; add .editorconfig Jan Polensky
2026-03-09 17:20 ` [LTP] [PATCH v1 1/3] fsetxattr02: Adapt test for kernel 7.0+ socket xattr support Jan Polensky
2026-03-10 13:25 ` Petr Vorel
2026-03-10 13:36 ` Petr Vorel
2026-03-11 14:54 ` Jan Polensky
2026-03-09 17:20 ` Jan Polensky [this message]
2026-03-09 17:20 ` [LTP] [PATCH v1 3/3] editorconfig: add consistent formatting rules for LTP Jan Polensky
2026-03-10 13:22 ` Petr Vorel
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=20260309172057.272946-3-japo@linux.ibm.com \
--to=japo@linux.ibm.com \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox