From: Greg KH <gregkh@linuxfoundation.org>
To: kernelci@lists.linux.dev
Cc: kernelci-results@groups.io, gus@collabora.com, stable@vger.kernel.org
Subject: Re: [REGRESSION] stable-rc/linux-5.10.y: (build) in vmlinux (Makefile:1212) [logspec:kbuild,kbuild.other]
Date: Tue, 11 Mar 2025 15:22:47 +0100 [thread overview]
Message-ID: <2025031121-aged-stand-c8f3@gregkh> (raw)
In-Reply-To: <CACo-S-0BKPQcA2Qh-7jmuU-YuX9E_wWcHEgr8pDhgwkzt0K5cQ@mail.gmail.com>
On Tue, Mar 11, 2025 at 01:47:06PM +0000, KernelCI bot wrote:
> Hello,
>
> New build issue found on stable-rc/linux-5.10.y:
>
> ---
> in vmlinux (Makefile:1212) [logspec:kbuild,kbuild.other]
> ---
>
> - dashboard: https://d.kernelci.org/issue/maestro:d5c2be698989c7de46471109aae8df0339b713c1
> - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> - commit HEAD: a0e8dfa03993fda7b4d4b696c50f69726522abba
>
>
> Log excerpt:
> =====================================================
> .lds
> In file included from ./include/linux/kernel.h:15,
> net/ipv6/udp.c: In function ‘udp_v6_send_skb’:
> ./include/linux/minmax.h:20:35: warning: comparison of distinct
> pointer types lacks a cast
> ./include/linux/minmax.h:26:18: note: in expansion of macro ‘__typecheck’
> ./include/linux/minmax.h:36:31: note: in expansion of macro ‘__safe_cmp’
> ./include/linux/minmax.h:45:25: note: in expansion of macro ‘__careful_cmp’
> net/ipv6/udp.c:1213:28: note: in expansion of macro ‘min’
> In file included from ./include/linux/uaccess.h:7,
> net/ipv4/udp.c: In function ‘udp_send_skb’:
> ./include/linux/minmax.h:20:35: warning: comparison of distinct
> pointer types lacks a cast
> ./include/linux/minmax.h:26:18: note: in expansion of macro ‘__typecheck’
> ./include/linux/minmax.h:36:31: note: in expansion of macro ‘__safe_cmp’
> ./include/linux/minmax.h:45:25: note: in expansion of macro ‘__careful_cmp’
> net/ipv4/udp.c:926:28: note: in expansion of macro ‘min’
This warnings I can understand, we'll just have to live with that.
But:
> FAILED unresolved symbol filp_close
What is that from?
Seems to be from 890ed45bde80 ("acct: block access to kernel internal
filesystems")? If so, that's really odd as this is not a new call to
this function, but just some additional ones.
thanks,
greg k-h
prev parent reply other threads:[~2025-03-11 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 13:47 [REGRESSION] stable-rc/linux-5.10.y: (build) in vmlinux (Makefile:1212) [logspec:kbuild,kbuild.other] KernelCI bot
2025-03-11 14:22 ` Greg KH [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=2025031121-aged-stand-c8f3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=gus@collabora.com \
--cc=kernelci-results@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=stable@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