All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: simplemessager@163.com
Cc: Meng Yang <yangm50@chinatelecom.cn>,
	ltp@lists.linux.it, Mingyu Li <limy83@chinatelecom.cn>
Subject: Re: [LTP] [PATCH 1/1] Skip wqueue testcases when KEY_NOTIFICATIONS not enabled.
Date: Mon, 8 Dec 2025 16:15:27 +0100	[thread overview]
Message-ID: <20251208151527.GA704055@pevik> (raw)
In-Reply-To: <20251205031719.53914-1-simplemessager@163.com>

Hi Mingyu, Meng,

I sent an alternative approach for this. Could you please retest it.

https://lore.kernel.org/ltp/20251208150542.704006-1-pvorel@suse.cz/T/#t
https://patchwork.ozlabs.org/project/ltp/list/?series=484779&state=*

> From: Mingyu Li <limy83@chinatelecom.cn>

> Skip wqueue testcases when KEY_NOTIFICATIONS not enabled.

> wqueue testcases relys on both CONFIG_WATCH_QUEUE
> and CONFIG_KEY_NOTIFICATIONS. keyctl will return EOPNOTSUPP
> when CONFIG_KEY_NOTIFICATIONS is not enabled and the wqueue
> testcases will failed when timeout. So we should skip
> testcases when we got EOPNOTSUPP from keyctl.

> Reported-by: Meng Yang <yangm50@chinatelecom.cn>
> Signed-off-by: Mingyu Li <limy83@chinatelecom.cn>
> ---
>  testcases/kernel/watchqueue/common.h | 22 ++++++++++++++++++++--
>  1 file changed, 20 insertions(+), 2 deletions(-)

> diff --git a/testcases/kernel/watchqueue/common.h b/testcases/kernel/watchqueue/common.h
> index 92e8f079c..e9100ab52 100644
> --- a/testcases/kernel/watchqueue/common.h
> +++ b/testcases/kernel/watchqueue/common.h
> @@ -85,8 +85,26 @@ static inline key_serial_t wqueue_add_key(int fd)
>  	if (key == -1)
>  		tst_brk(TBROK, "add_key error: %s", tst_strerrno(errno));

> -	keyctl(KEYCTL_WATCH_KEY, key, fd, 0x01);
> -	keyctl(KEYCTL_WATCH_KEY, KEY_SPEC_SESSION_KEYRING, fd, 0x02);
> +	TEST(keyctl(KEYCTL_WATCH_KEY, key, fd, 0x01));
> +	if (TST_RET) {
> +		switch (TST_ERR) {
> +		case EOPNOTSUPP:
> +			tst_brk(TCONF | TTERRNO, "CONFIG_KEY_NOTIFICATION is not set!");
nit: "| TTERRNO" is not needed, because we know the content of errno:
EOPNOTSUPP.

> +			break;
> +		default:
> +			tst_res(TINFO, "CONFIG_KEY_NOTIFICATION is set.");
> +		}

If your approach is taken, I would simplify it (we don't need TINFO)

	if (keyctl(KEYCTL_WATCH_KEY, key, fd, 0x01) && errno == EOPNOTSUPP)
			tst_brk(TCONF, "CONFIG_KEY_NOTIFICATION is not set!");

	if (keyctl(KEYCTL_WATCH_KEY, KEY_SPEC_SESSION_KEYRING, fd, 0x02) && errno == EOPNOTSUPP)
			tst_brk(TCONF, "CONFIG_KEY_NOTIFICATION is not set!");

Kind regards,
Petr

> +	}
> +	TEST(keyctl(KEYCTL_WATCH_KEY, KEY_SPEC_SESSION_KEYRING, fd, 0x02));
> +	if (TST_RET) {
> +		switch (TST_ERR) {
> +		case EOPNOTSUPP:
> +			tst_brk(TCONF | TTERRNO, "CONFIG_KEY_NOTIFICATION is not set!");
> +			break;
> +		default:
> +			tst_res(TINFO, "CONFIG_KEY_NOTIFICATION is set.");
> +		}
> +	}

>  	return key;
>  }

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-12-08 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05  3:17 [LTP] [PATCH 1/1] Skip wqueue testcases when KEY_NOTIFICATIONS not enabled simplemessager
2025-12-08 15:15 ` Petr Vorel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-05  3:00 simplemessager
2025-12-11 10:31 ` Andrea Cervesato via ltp

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=20251208151527.GA704055@pevik \
    --to=pvorel@suse.cz \
    --cc=limy83@chinatelecom.cn \
    --cc=ltp@lists.linux.it \
    --cc=simplemessager@163.com \
    --cc=yangm50@chinatelecom.cn \
    /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.