public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	Christian Brauner <brauner@kernel.org>,
	Andrey Albershteyn <aalbersh@kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Arnd Bergmann <arnd@arndb.de>,
	open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Ben Copeland <benjamin.copeland@linaro.org>,
	linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>,
	LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] 6.18.0-rc1: LTP syscalls ioctl_pidfd05: TFAIL: ioctl(pidfd, PIDFD_GET_INFO_SHORT, info_invalid) expected EINVAL: ENOTTY (25)
Date: Fri, 17 Oct 2025 11:25:10 +0200	[thread overview]
Message-ID: <aPILdh2XzsYgEg66@yuki.lan> (raw)
In-Reply-To: <CA+G9fYtUp3Bk-5biynickO5U98CKKN1nkE7ooxJHp7dT1g3rxw@mail.gmail.com>

Hi!
> > The LTP syscalls ioctl_pidfd05 test failed due to following error on
> > the Linux mainline
> > kernel v6.18-rc1-104-g7ea30958b305 on the arm64, arm and x86_64.
> >
> > The Test case is expecting to fail with EINVAL but found ENOTTY.
> 
> [Not a kernel regression]
> 
> From the recent LTP upgrade we have newly added test cases,
> ioctl_pidfd()
> 
> The test case is meant to test,
> 
> Add ioctl_pidfd05 test
> Verify that ioctl() raises an EINVAL error when PIDFD_GET_INFO
>  is used.
>  This happens when:
>    - info parameter is NULL
>    - info parameter is providing the wrong size
> 
> However, we need to investigate the reason for failure.
> 
> Test case: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/ioctl/ioctl_pidfd05.c

Already fixed in:

commit 00c3e947cece63ce81cdaf12b5a2071984aa7815
Author: Avinesh Kumar <akumar@suse.de>
Date:   Thu Sep 25 10:19:11 2025 +0200

    Introduce ioctl_pidfd_get_info_supported() function

    Check if ioctl(PIDFD_GET_INFO) is implemented or not
    before proceeding in ioctl_pidfd05 test.


-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2025-10-17  9:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+G9fYuF44WkxhDj9ZQ1+PwdsU_rHGcYoVqMDr3AL=AvweiCxg@mail.gmail.com>
2025-10-17  9:20 ` [LTP] 6.18.0-rc1: LTP syscalls ioctl_pidfd05: TFAIL: ioctl(pidfd, PIDFD_GET_INFO_SHORT, info_invalid) expected EINVAL: ENOTTY (25) Naresh Kamboju
2025-10-17  9:25   ` Cyril Hrubis [this message]
2025-10-17  9:40   ` Cyril Hrubis
2025-10-17 12:43     ` Jan Kara
2025-10-21 13:21       ` Christian Brauner via ltp
2025-10-21 20:48         ` Jan Kara
2025-10-22  7:51           ` Petr Vorel
2025-10-22  8:10             ` Naresh Kamboju

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=aPILdh2XzsYgEg66@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=aalbersh@kernel.org \
    --cc=arnd@arndb.de \
    --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@lists.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