From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Voegtle" <tv@lio96.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Build error kernel/cgroup/rstat.c on v6.7-1959-gaffc5af36bbb
Date: Thu, 11 Jan 2024 00:10:24 +0100 [thread overview]
Message-ID: <91fe3dea-ca35-4dc9-ac13-e4eb0df30951@app.fastmail.com> (raw)
In-Reply-To: <c6c5fe88-c024-40db-ad1c-4e6681e3d7af@lio96.de>
On Wed, Jan 10, 2024, at 22:18, Thomas Voegtle wrote:
> On Wed, 10 Jan 2024, Arnd Bergmann wrote:
>
>> On Wed, Jan 10, 2024, at 20:50, Thomas Voegtle wrote:
>>> Hello,
>>>
>>> building v6.7-1959-gaffc5af36bbb I get this:
>>>
>>> ...
>>> CALL scripts/checksyscalls.sh
>>> DESCEND objtool
>>> INSTALL libsubcmd_headers
>>> CC kernel/cgroup/rstat.o
>>> kernel/cgroup/rstat.c:218:22: error: no previous prototype for
>>> ‘bpf_rstat_flush’ [-Werror=missing-prototypes]
>>> __weak noinline void bpf_rstat_flush(struct cgroup *cgrp,
>>> ^~~~~~~~~~~~~~~
>>>
>>>
>>> git bisects points to:
>>>
>>> commit 0fcb70851fbfea1776ae62f67c503fef8f0292b9 (refs/bisect/bad)
>>> Author: Arnd Bergmann <arnd@arndb.de>
>>> Date: Thu Nov 23 12:05:06 2023 +0100
>>>
>>> Makefile.extrawarn: turn on missing-prototypes globally
>>>
>>>
>>> My config is attached.
>>> openSUSE Leap 15.5 x86_64 with gcc 7.5.0
>>>
>>>
>>> Is this already known?
>>
>> There is a workaround in linux-next, see commit
>> 15fb6f2b6c4c ("bpf: Add __bpf_hook_{start,end} macros")
>>
>> I assume this will be merged soon.
>
> That commit is already merged?
It's probably missing this one then:
689b097a06ba ("compiler-gcc: Suppress -Wmissing-prototypes warning for all supported GCC")
Arnd
next prev parent reply other threads:[~2024-01-10 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 19:50 Thomas Voegtle
2024-01-10 20:41 ` Arnd Bergmann
2024-01-10 21:18 ` Thomas Voegtle
2024-01-10 23:10 ` Arnd Bergmann [this message]
2024-01-11 8:38 ` Thomas Voegtle
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=91fe3dea-ca35-4dc9-ac13-e4eb0df30951@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tv@lio96.de \
/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
all inboxes | Powered by JetHome®