[PATCH 02/13] Update PIDFD_* constants for Linux 6.17

[Yury Khrustalev]

* Florian

On Thu, Nov 20, 2025 at 03:01:21PM +0100, Florian Weimer wrote:
> * Yury Khrustalev:
> 
> > On Fri, Nov 07, 2025 at 09:56:43AM +0000, Yury Khrustalev wrote:
> >> ...
> >>
> >> And on system with 6.17 I get:
> >> 
> >>   $ strace -e trace=ioctl -ff ./misc/tst-pidfd_getinfo
> >>   strace: Process 5279 attached
> >>   [pid  5279] ioctl(3, PIDFD_GET_INFO, 0xfffffffff308) = 0
> >>   [pid  5279] +++ exited with 0 +++
> >>   --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5279, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
> >>   +++ exited with 0 +++
> >> 
> >> So, I think that the test should expect EINVAL for an unsupported flag,
> >> in which case the test should be UNSUPPORTED.
> >
> > Is there a BZ for this? I can send a patch with a fix if this helps.
> 
> What would be the fix be?

See above: we should expect EINVAL as a valid response and exit from the
test as UNSUPPORTED.

> I think if the UAPI headers are wrong, the test should fail.

I wasn't looking at the headers, I was reading man for ioctl:

  EINVAL op or argp is not valid.

Thanks,
Yury