From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave.anglin@bell.net>,
linux-parisc <linux-parisc@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>
Subject: Re: PIDFD_GET_INFO
Date: Fri, 21 Nov 2025 22:05:20 +0100 [thread overview]
Message-ID: <092acd39-3783-4f33-a26d-e6b4f8dfdf1a@gmx.de> (raw)
In-Reply-To: <2380a8de-5284-49f3-8155-f7fb9496b422@bell.net>
On 11/21/25 20:04, John David Anglin wrote:
> We have a new glibc failure that may be a kernel issue:
>
> make[2]: Entering directory '/home/dave/gnu/glibc/glibc/misc'
> env GCONV_PATH=/home/dave/gnu/glibc/objdir/iconvdata LOCPATH=/home/dave/gnu/glibc/objdir/localedata LC_ALL=C
> /home/dave/gnu/glibc/objdir/elf/ld.so.1 --library-path
> /home/dave/gnu/glibc/objdir:/home/dave/gnu/glibc/objdir/math:/home/dave/gnu/glibc/objdir/elf:/home/dave/gnu/glibc/objdir/dlfcn:/home/dave/gnu/glibc/objdir/nss:/home/dave/gnu/glibc/objdir/nis:/home/dave/gnu/glibc/objdir/rt:/home/dave/gnu/glibc/objdir/resolv:/home/dave/gnu/glibc/objdir/mathvec:/home/dave/gnu/glibc/objdir/support:/home/dave/gnu/glibc/objdir/misc:/home/dave/gnu/glibc/objdir/debug:/home/dave/gnu/glibc/objdir/nptl:/usr/lib/gcc/hppa-linux-gnu/15/../../../hppa-linux-gnu/:/usr/lib/gcc/hppa-linux-gnu/15/../../../hppa-linux-gnu/
> /home/dave/gnu/glibc/objdir/misc/tst-pidfd_getinfo > /home/dave/gnu/glibc/objdir/misc/tst-pidfd_getinfo.out; \
> ../scripts/evaluate-test.sh misc/tst-pidfd_getinfo $? false false > /home/dave/gnu/glibc/objdir/misc/tst-pidfd_getinfo.test-result
> make[2]: Leaving directory '/home/dave/gnu/glibc/glibc/misc'
> FAIL: misc/tst-pidfd_getinfo
> original exit status 1
> error: ../sysdeps/unix/sysv/linux/tst-pidfd_getinfo.c:52: ioctl (PIDFD_GET_INFO) failed: Invalid argument
> error: 1 test failures
>
> if (ioctl (pidfd, PIDFD_GET_INFO, &info) != 0)
> {
> if (errno == ENOTTY)
> FAIL_UNSUPPORTED ("kernel does not support PIDFD_GET_INFO");
> else
> FAIL_EXIT1 ("ioctl (PIDFD_GET_INFO) failed: %m");
> }
Which kernel are you running?
I could reproduce the issue with 6.12.33+deb13-parisc64, but
it's fixed in git head (6.18-rc1, in both compat-32bit and native mode).
There have been quite some changes in between those versions, so
maybe there is at least one patch missing backporting?
Helge
next prev parent reply other threads:[~2025-11-21 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 19:04 PIDFD_GET_INFO John David Anglin
2025-11-21 21:05 ` Helge Deller [this message]
2025-11-21 21:17 ` PIDFD_GET_INFO John David Anglin
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=092acd39-3783-4f33-a26d-e6b4f8dfdf1a@gmx.de \
--to=deller@gmx.de \
--cc=brauner@kernel.org \
--cc=dave.anglin@bell.net \
--cc=linux-parisc@vger.kernel.org \
/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