From: KernelCI bot <bot@kernelci•org>
To: kernelci-results@groups•io
Cc: regressions@lists•linux.dev, gus@collabora•com,
linux-next@vger•kernel.org
Subject: [REGRESSION] next/master: (build) in expansion of macro ‘min’ in fs/fuse/file.o (fs/fuse/file.c) [lo...
Date: Tue, 16 Dec 2025 02:59:03 -0000 [thread overview]
Message-ID: <176585394290.2610.8656861889938723251@77bfb67944a2> (raw)
Hello,
New build issue found on next/master:
---
in expansion of macro ‘min’ in fs/fuse/file.o (fs/fuse/file.c) [logspec:kbuild,kbuild.compiler.note]
---
- dashboard: https://d.kernelci.org/i/maestro:efd5e2937b906561246dc835406f3fd74dd15d9d
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- commit HEAD: 563c8dd425b59e44470e28519107b1efc99f4c7b
- tags: next-20251216
Please include the KernelCI tag when submitting a fix:
Reported-by: kernelci.org bot <bot@kernelci•org>
Log excerpt:
=====================================================
fs/fuse/file.c:1326:16: note: in expansion of macro ‘min’
1326 | return min(((pos + len - 1) >> PAGE_SHIFT) - (pos >> PAGE_SHIFT) + 1,
| ^~~
=====================================================
# Builds where the incident occurred:
## 32r2el_defconfig on (mips):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-mips-32r2el_defconfig-6940c4b8cbfd84c3cdba9ce1/.config
- dashboard: https://d.kernelci.org/build/maestro:6940c4b8cbfd84c3cdba9ce1
#kernelci issue maestro:efd5e2937b906561246dc835406f3fd74dd15d9d
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists•linux.dev
Made with love by the KernelCI team - https://kernelci.org
next reply other threads:[~2025-12-16 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 2:59 KernelCI bot [this message]
2025-12-16 3:30 ` [REGRESSION] next/master: (build) in expansion of macro ‘min’ in fs/fuse/file.o (fs/fuse/file.c) [lo Randy Dunlap
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=176585394290.2610.8656861889938723251@77bfb67944a2 \
--to=bot@kernelci$(echo .)org \
--cc=gus@collabora$(echo .)com \
--cc=kernelci-results@groups$(echo .)io \
--cc=kernelci@lists$(echo .)linux.dev \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=regressions@lists$(echo .)linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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