From: Sasha Levin <sashal@kernel.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Sami Tolvanen <samitolvanen@google.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, florian.fainelli@broadcom.com,
pavel@denx.de
Subject: Re: [PATCH 6.7 000/707] 6.7.11-rc2 review
Date: Tue, 26 Mar 2024 07:23:23 -0400 [thread overview]
Message-ID: <ZgKwK4-S9uIaaMKD@sashalap> (raw)
In-Reply-To: <CAEUSe78CQrHFEz92svQKuvjU91FDc=Dt+NNf_5_=pKeE22TzXg@mail.gmail.com>
On Mon, Mar 25, 2024 at 01:47:40PM -0600, Daniel Díaz wrote:
>Hello!
>
>On Mon, 25 Mar 2024 at 12:14, Sami Tolvanen <samitolvanen@google.com> wrote:
>> On Mon, Mar 25, 2024 at 11:43:48AM -0600, Daniel Díaz wrote:
>> > Hello!
>> >
>> > On 25/03/24 6:00 a. m., Sasha Levin wrote:
>> > > This is the start of the stable review cycle for the 6.7.11 release.
>> > > There are 707 patches in this series, all will be posted as a response
>> > > to this one. If anyone has any issues with these being applied, please
>> > > let me know.
>> > >
>> > > Responses should be made by Wed Mar 27 12:00:02 PM UTC 2024.
>> > > Anything received after that time might be too late.
>> > >
>> > > The whole patch series can be found in one patch at:
>> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-6.7.y&id2=v6.7.10
>> > > or in the git tree and branch at:
>> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.7.y
>> > > and the diffstat can be found below.
>> > >
>> > > Thanks,
>> > > Sasha
>> >
>> > We see *lots* of new warnings in RISC-V with Clang 17. Here's one:
>> >
>> > -----8<-----
>> > /builds/linux/mm/oom_kill.c:1195:1: warning: unused function '___se_sys_process_mrelease' [-Wunused-function]
>> > 1195 | SYSCALL_DEFINE2(process_mrelease, int, pidfd, unsigned int, flags)
>> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > /builds/linux/include/linux/syscalls.h:221:36: note: expanded from macro 'SYSCALL_DEFINE2'
>> > 221 | #define SYSCALL_DEFINE2(name, ...) SYSCALL_DEFINEx(2, _##name, __VA_ARGS__)
>> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > /builds/linux/include/linux/syscalls.h:231:2: note: expanded from macro 'SYSCALL_DEFINEx'
>> > 231 | __SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
>> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > /builds/linux/arch/riscv/include/asm/syscall_wrapper.h:81:2: note: expanded from macro '__SYSCALL_DEFINEx'
>> > 81 | __SYSCALL_SE_DEFINEx(x, sys, name, __VA_ARGS__) \
>> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > /builds/linux/arch/riscv/include/asm/syscall_wrapper.h:40:14: note: expanded from macro '__SYSCALL_SE_DEFINEx'
>> > 40 | static long ___se_##prefix##name(__MAP(x,__SC_LONG,__VA_ARGS__))
>> > | ^~~~~~~~~~~~~~~~~~~~
>> > <scratch space>:30:1: note: expanded from here
>> > 30 | ___se_sys_process_mrelease
>> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~
>> > 1 warning generated.
>> > ----->8-----
>>
>> Yup, I can reproduce this with ToT Clang. It looks like the alias
>> isn't sufficient for Clang and we need to add an explicit __used
>> attribute. Can you confirm if this patch fixes the issue for you?
>>
>> diff --git a/arch/riscv/include/asm/syscall_wrapper.h b/arch/riscv/include/asm/syscall_wrapper.h
>> index 980094c2e976..ac80216549ff 100644
>> --- a/arch/riscv/include/asm/syscall_wrapper.h
>> +++ b/arch/riscv/include/asm/syscall_wrapper.h
>> @@ -36,7 +36,8 @@ asmlinkage long __riscv_sys_ni_syscall(const struct pt_regs *);
>> ulong) \
>> __attribute__((alias(__stringify(___se_##prefix##name)))); \
>> __diag_pop(); \
>> - static long noinline ___se_##prefix##name(__MAP(x,__SC_LONG,__VA_ARGS__)); \
>> + static long noinline ___se_##prefix##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
>> + __used; \
>> static long ___se_##prefix##name(__MAP(x,__SC_LONG,__VA_ARGS__))
>
>It does: the hundreds of warnings are gone. Build-tested with Clang
I'm assuming this fix needs to land upstream, and isn't specific for
stable?
I'll drop the offending commit for now, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-03-26 11:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:00 [PATCH 6.7 000/707] 6.7.11-rc2 review Sasha Levin
2024-03-25 17:43 ` Daniel Díaz
2024-03-25 18:14 ` Sami Tolvanen
2024-03-25 19:47 ` Daniel Díaz
2024-03-26 11:23 ` Sasha Levin [this message]
2024-03-25 17:57 ` SeongJae Park
2024-03-25 18:22 ` Naresh Kamboju
2024-03-25 19:07 ` Pavel Machek
2024-03-25 20:05 ` Justin Forbes
2024-03-25 20:39 ` Florian Fainelli
2024-03-26 2:09 ` Bagas Sanjaya
2024-03-26 9:04 ` Ron Economos
2024-03-26 16:16 ` Mark Brown
2024-03-26 17:28 ` Greg KH
2024-03-26 17:35 ` Mark Brown
2024-03-26 17:00 ` Shuah Khan
2024-03-26 19:52 ` Conor Dooley
2024-03-26 20:48 ` Shreeya Patel
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=ZgKwK4-S9uIaaMKD@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=daniel.diaz@linaro.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=palmer@dabbelt.com \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=samitolvanen@google.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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