From: Petr Vorel <pvorel@suse.cz>
To: Jan Polensky <japo@linux.ibm.com>,
chrubis@suse.cz, Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v1 1/3] fsetxattr02: Adapt test for kernel 7.0+ socket xattr support
Date: Tue, 10 Mar 2026 14:36:39 +0100 [thread overview]
Message-ID: <20260310133639.GE39882@pevik> (raw)
In-Reply-To: <20260310132522.GD39882@pevik>
Hi Jan,
> Hi Jan,
> > 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).
I double checked kernel version for dc0876b9846d.
$ git tag --contains dc0876b9846d3d48bb8528332106d1b051578a02
next-20260305
next-20260306
next-20260309
=> IMHO it will be for v7.1. And indeed, current LTP master works on openSUSE
7.0.0-rc2-2.g0bfc1b0-default kernel and fails with your patch.
> Good catch, thanks!
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> > Adapts the test to expect success (exp_err = 0) instead of EPERM when
> > testing fsetxattr(2) on sockets with kernel 7.0+.
> > Signed-off-by: Jan Polensky <japo@linux.ibm.com>
> > ---
> > testcases/kernel/syscalls/fsetxattr/fsetxattr02.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> > diff --git a/testcases/kernel/syscalls/fsetxattr/fsetxattr02.c b/testcases/kernel/syscalls/fsetxattr/fsetxattr02.c
> > index 18490a865871..ede86b218ee6 100644
> > --- a/testcases/kernel/syscalls/fsetxattr/fsetxattr02.c
> > +++ b/testcases/kernel/syscalls/fsetxattr/fsetxattr02.c
> > @@ -158,6 +158,10 @@ static void verify_fsetxattr(unsigned int i)
> > if (TST_RET == -1 && TST_ERR == EOPNOTSUPP)
> > tst_brk(TCONF, "fsetxattr(2) not supported");
> > + /* consider newer kernels */
> very nit: The commit is obvious. If anything to add, I would add the git hash itself.
> Kind regards,
> Petr
> > + if ((tst_kvercmp(7, 0, 0) >= 0) && (strncmp(tc[i].fname, SOCK, strlen(SOCK)) == 0))
> > + tc[i].exp_err = 0;
It should be tst_kvercmp(7, 1, 0) >= 0
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-10 13:37 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 [this message]
2026-03-11 14:54 ` Jan Polensky
2026-03-09 17:20 ` [LTP] [PATCH v1 2/3] setxattr02: " Jan Polensky
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=20260310133639.GE39882@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=japo@linux.ibm.com \
--cc=ltp@lists.linux.it \
/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