From: Petr Vorel <pvorel@suse.cz>
To: simplemessager@163.com
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] safe_keyctl: Skip with TCONF on EOPNOTSUPP
Date: Fri, 12 Dec 2025 16:21:54 +0100 [thread overview]
Message-ID: <20251212152154.GA165966@pevik> (raw)
In-Reply-To: <20251211081205.342673-2-simplemessager@163.com>
> From: Petr Vorel <pvorel@suse.cz>
> errno EOPNOTSUPP is likely a configuration issue, skip testing
> with TCONF.
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> Signed-off-by: Mingyu Li <limy83@chinatelecom.cn>
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> ---
> include/lapi/keyctl.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
> diff --git a/include/lapi/keyctl.h b/include/lapi/keyctl.h
> index e08b8f132..eac9e2609 100644
> --- a/include/lapi/keyctl.h
> +++ b/include/lapi/keyctl.h
> @@ -212,7 +212,8 @@ static inline long safe_keyctl(const char *file, const int lineno,
> rval = keyctl(cmd, arg2, arg3, arg4, arg5);
> if (rval == -1) {
> - tst_brk_(file, lineno, TBROK | TERRNO,
> + tst_brk_(file, lineno,
> + errno == EOPNOTSUPP ? TCONF : TBROK | TERRNO,
In the end, thinking about it twice I merged version which always prints TERRNO,
because we don't have any special explanation for TCONF, therefore the only
explanation is the errno itself:
(errno == EOPNOTSUPP ? TCONF : TBROK) | TERRNO,
Merged, with your Reviewed-by: and Co-developed-by:. Thanks!
Kind regards,
Petr
> "keyctl(%d, %lu, %lu, %lu, %lu)",
> cmd, arg2, arg3, arg4, arg5);
> }
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-12-12 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 15:05 [LTP] [PATCH 0/2] safe_keyctl: Skip with TCONF on EOPNOTSUPP Petr Vorel
2025-12-08 15:05 ` [LTP] [PATCH 1/2] " Petr Vorel
2025-12-09 19:48 ` Petr Vorel
2025-12-08 15:05 ` [LTP] [PATCH 2/2] wqueue0*: Use SAFE_KEYCTL() Petr Vorel
2025-12-12 15:22 ` Petr Vorel
2025-12-09 12:29 ` [LTP] [PATCH 0/2] safe_keyctl: Skip with TCONF on EOPNOTSUPP simplemessager
2025-12-09 12:29 ` [LTP] [PATCH] " simplemessager
2025-12-09 12:37 ` [LTP] [PATCH 0/2] " simplemessager
2025-12-09 12:37 ` [LTP] [PATCH] " simplemessager
2025-12-09 19:53 ` Petr Vorel
2025-12-11 8:11 ` simplemessager
2025-12-11 8:11 ` [LTP] [PATCH 1/1] " simplemessager
2025-12-12 15:21 ` Petr Vorel [this message]
2025-12-09 19:50 ` [LTP] [PATCH 0/2] " 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=20251212152154.GA165966@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=simplemessager@163.com \
/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