From: Randy Dunlap <rdunlap@infradead•org>
To: kernelci@lists•linux.dev, kernelci-results@groups•io
Cc: regressions@lists•linux.dev, gus@collabora•com,
linux-next@vger•kernel.org
Subject: Re: [REGRESSION] next/master: (build) in expansion of macro ‘min’ in fs/fuse/file.o (fs/fuse/file.c) [lo...
Date: Mon, 15 Dec 2025 19:30:36 -0800 [thread overview]
Message-ID: <5f36adcb-9f5e-4366-88eb-9afd001fa981@infradead.org> (raw)
In-Reply-To: <176585394290.2610.8656861889938723251@77bfb67944a2>
Hi,
On 12/15/25 6:59 PM, KernelCI bot wrote:
>
>
>
>
> 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]
> ---
Please include the complete [compiler] error/warning message in your emails.
There is no error/warning message here.
[/me looks on dashboard]
Still difficult to see an error/warning message.
Something under Misc Data + logspec says:
{"error":{"script":"scripts/Makefile.build:287","target":"fs/fuse/file.o","line_no":"1326","position":"16","src_file":"fs/fuse/file.c","error_type":"kbuild.compiler.note","log_excerpt":"fs/fuse/file.c:1326:16: note: in expansion of macro ‘min’\n 1326 | return min(((pos + len - 1) >> PAGE_SHIFT) - (pos >> PAGE_SHIFT) + 1,\n | ^~~\n","error_summary":"in expansion of macro ‘min’","signature_loc":"4a58a6a015a10073943adaad7c190fcd06e14dd4","signature_fields":{"target":"fs/fuse/file.o","line_no":"1326","position":"16","src_file":"fs/fuse/file.c","error_type":"kbuild.compiler.note","error_summary":"in expansion of macro ‘min’"}},"parser":"kbuild","version":"1.0.0"}
That's not good for a build error report.
>
> - 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
>
--
~Randy
prev parent reply other threads:[~2025-12-16 3:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 2:59 [REGRESSION] next/master: (build) in expansion of macro ‘min’ in fs/fuse/file.o (fs/fuse/file.c) [lo KernelCI bot
2025-12-16 3:30 ` Randy Dunlap [this message]
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=5f36adcb-9f5e-4366-88eb-9afd001fa981@infradead.org \
--to=rdunlap@infradead$(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