From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
clang-built-linux <llvm@lists.linux.dev>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
linux-s390@vger.kernel.org,
"open list" <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, samba-technical@lists.samba.org,
linux-cifs@vger.kernel.org,
"Nathan Chancellor" <nathan@kernel.org>
Cc: "Steve French" <sfrench@samba.org>,
bharathsm@microsoft.com,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Shyam Prasad N" <sprasad@microsoft.com>
Subject: Re: clang-nightly: ERROR: modpost: "wcslen" [fs/smb/client/cifs.ko] undefined!
Date: Wed, 02 Apr 2025 15:02:29 +0200 [thread overview]
Message-ID: <3ad96ab5-72a3-48ee-8ab3-e68d066169a4@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYuQHeGicnEx1d=XBC0p1LCsndi5q0p86V7pCZ02d8Fv_w@mail.gmail.com>
On Wed, Apr 2, 2025, at 14:21, Naresh Kamboju wrote:
> Build regression: arm powerpc s390 modpost "wcslen" fs smb client
> cifs.ko undefined
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ## Build log
>
> ERROR: modpost: "wcslen" [fs/smb/client/cifs.ko] undefined!
This is from the latest clang release, and Nathan already sent a fix:
https://lore.kernel.org/lkml/20250328-string-add-wcslen-for-llvm-opt-v3-1-a180b4c0c1c4@kernel.org/
Arnd
prev parent reply other threads:[~2025-04-02 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 12:21 clang-nightly: ERROR: modpost: "wcslen" [fs/smb/client/cifs.ko] undefined! Naresh Kamboju
2025-04-02 13:02 ` Arnd Bergmann [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=3ad96ab5-72a3-48ee-8ab3-e68d066169a4@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=bharathsm@microsoft.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=sprasad@microsoft.com \
--cc=torvalds@linux-foundation.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