public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: arnd@kernel.org, brauner@kernel.org, jack@suse.cz,
	regressions@lists.linux.dev, arnd@arndb.de,
	linux-kernel@vger.kernel.org, lkft-triage@lists.linaro.org,
	lkft-triage@linaro.org, ltp@lists.linux.it,
	benjamin.copeland@linaro.org, linux-fsdevel@vger.kernel.org,
	aalbersh@kernel.org, lkft@linaro.org, dan.carpenter@linaro.org,
	viro@zeniv.linux.org.uk
Subject: Re: [LTP] [PATCH] ioctl_pidfd05: accept both EINVAL and ENOTTY as valid errors
Date: Wed, 22 Oct 2025 14:12:03 +0200	[thread overview]
Message-ID: <20251022121203.GA481852@pevik> (raw)
In-Reply-To: <20251022115704.46936-1-naresh.kamboju@linaro.org>

Hi Naresh,

> Latest kernels return ENOTTY instead of EINVAL when invoking
> ioctl(pidfd, PIDFD_GET_INFO_SHORT, info_invalid).  Update the test to
> accept both EINVAL and ENOTTY as valid errors to ensure compatibility
> across different kernel versions.

Thanks a lot for contributing to LTP, we really appreciate it.

> Link: https://lore.kernel.org/all/CA+G9fYtUp3Bk-5biynickO5U98CKKN1nkE7ooxJHp7dT1g3rxw@mail.gmail.com
very nit: +1 for this. I prefer to reference it differently (e.g. [1]) as I add
Link: for referencing your actual patch the same way how it's used in kernel.
(e.g. Link: https://lore.kernel.org/ltp/20251022115704.46936-1-naresh.kamboju@linaro.org/)

> +++ b/testcases/kernel/syscalls/ioctl/ioctl_pidfd05.c
> @@ -4,7 +4,7 @@
>   */

>  /*\
> - * Verify that ioctl() raises an EINVAL error when PIDFD_GET_INFO is used. This
> + * Verify that ioctl() raises an EINVAL or ENOTTY error when PIDFD_GET_INFO is used. This
nit: maybe note for ENOTTY: (from v6.18)?
>   * happens when:
>   *
>   * - info parameter is NULL
> @@ -14,6 +14,7 @@
>  #include "tst_test.h"
>  #include "lapi/pidfd.h"
>  #include "lapi/sched.h"
> +#include <errno.h>
>  #include "ioctl_pidfd.h"

>  struct pidfd_info_invalid {
> @@ -43,7 +44,22 @@ static void run(void)
>  		exit(0);

>  	TST_EXP_FAIL(ioctl(pidfd, PIDFD_GET_INFO, NULL), EINVAL);
> -	TST_EXP_FAIL(ioctl(pidfd, PIDFD_GET_INFO_SHORT, info_invalid), EINVAL);
> +	/* Expect ioctl to fail; accept either EINVAL or ENOTTY */
> +	TEST(ioctl(pidfd, PIDFD_GET_INFO_SHORT, info_invalid));

I'm sorry, we prefer these macros in include/tst_test_macros.h which shorten the
code. Could you please use TST_EXP_FAIL_ARR() [1]?

Kind regards,
Petr

[1] https://linux-test-project.readthedocs.io/en/latest/developers/api_c_tests.html#macro-tst-exp-fail-arr

> +	if (TEST_RETURN == -1) {
> +		if (TEST_ERRNO == EINVAL || TEST_ERRNO == ENOTTY) {
> +			tst_res(TPASS,
> +				"ioctl(PIDFD_GET_INFO_SHORT) failed as expected with %s",
> +				tst_strerrno(TEST_ERRNO));
> +		} else {
> +			tst_res(TFAIL,
> +				"Unexpected errno: %s (expected EINVAL or ENOTTY)",
> +				tst_strerrno(TEST_ERRNO));
> +		}
> +	} else {
> +		tst_res(TFAIL, "ioctl(PIDFD_GET_INFO_SHORT) unexpectedly succeeded");
> +	}
> +

>  	SAFE_CLOSE(pidfd);
>  }

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

      reply	other threads:[~2025-10-22 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 11:57 [LTP] [PATCH] ioctl_pidfd05: accept both EINVAL and ENOTTY as valid errors Naresh Kamboju
2025-10-22 12:12 ` Petr Vorel [this message]

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=20251022121203.GA481852@pevik \
    --to=pvorel@suse.cz \
    --cc=aalbersh@kernel.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=benjamin.copeland@linaro.org \
    --cc=brauner@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@linaro.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=lkft@linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@lists.linux.dev \
    --cc=viro@zeniv.linux.org.uk \
    /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