[Bug build/34031] New: ppc64le misc/tst-pidfd-consts fail for mismatching PIDFD_SELF_*

[fche at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=34031

            Bug ID: 34031
           Summary: ppc64le  misc/tst-pidfd-consts fail for mismatching
                    PIDFD_SELF_*
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: carlos at redhat dot com
  Target Milestone: ---

On the `glibc-fedora-ppc64le` buildbot, there is a consistent failure in
**`misc/tst-pidfd-consts.out`**. 
The test log shows:
```text
First source:
#include <sys/pidfd.h>

Second source:
#include <asm/fcntl.h>
#include <linux/pidfd.h>

Different values for PIDFD_SELF_PROCESS: -10001 != -20000
Different values for PIDFD_SELF_THREAD_GROUP: -10001 != -20000
```
**Why it's interesting:** This points directly to a discrepancy between the
glibc-provided headers (`sys/pidfd.h`) and the kernel-provided headers
(`linux/pidfd.h`) for the PowerPC architecture, likely meaning these macros are
out of sync for PPC in upstream glibc.


Problem identified/triaged with LLM + bunsen-MCP.  Test results may be
confirmed manually via bunsen web interface.


https://builder.sourceware.org/testruns/?op_mode=search_exact&maxdelta=3&search_direction=maxdelta_around&form2_has_keyvalue_k=testrun.gitdescribe&form2_has_keyvalue_v=*&form2_has_keyvalue_op=glob&form2_has_keyvalue2_k=omnitest.results&form2_has_keyvalue2_v=*&form2_has_keyvalue2_op=glob&has_keyvalue_k=source.gitrepo.canon&has_keyvalue_op=%3D&has_keyvalue_v=sourceware.org%2Fgit%2Fglibc.git&has_keyvalue2_k=uname-m&has_keyvalue2_op=glob&has_keyvalue2_v=ppc64le&cust_cols=source.gitrepo&cust_cols=omnitest.results&order_by=testrun.authored.time&order=desc&limit=1000&offset=0&offset=0&per_page_selector=10&reset_search_form=no

-- 
You are receiving this mail because:
You are on the CC list for the bug.