From: Chris Clayton <chris2553@googlemail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 6.3.1
Date: Tue, 2 May 2023 14:12:58 +0100 [thread overview]
Message-ID: <c7842e46-fc41-c989-b5e7-ec504cd0c8f2@googlemail.com> (raw)
In-Reply-To: <2023050201-bluish-habitable-474a@gregkh>
Hi Greg
On 02/05/2023 08:31, Greg Kroah-Hartman wrote:
> On Tue, May 02, 2023 at 08:43:47AM +0900, Greg Kroah-Hartman wrote:
>> On Tue, May 02, 2023 at 06:40:03AM +0900, Greg Kroah-Hartman wrote:
>>> On Mon, May 01, 2023 at 07:22:56AM +0100, Chris Clayton wrote:
>>>> 6.3.1 FTBFS thusly:
>>>
>>> What is "FTBFS"?
>>>
>>>> drivers/net/wireguard/timers.c: In function 'wg_expired_retransmit_handshake':
>>>> <command-line>: error: format '%d' expects argument of type 'int', but argument 6 has type 'long unsigned int'
>>>> [-Werror=format=]
>>>> <command-line>: note: in expansion of macro 'KBUILD_MODNAME'
>>>> ./include/linux/dynamic_debug.h:223:29: note: in expansion of macro 'pr_fmt'
>>>> 223 | func(&id, ##__VA_ARGS__); \
>>>> | ^~~~~~~~~~~
>>>
>>> <snip>
>>>
>>>> There's a patch to drivers/net/wireguard/timers.c that fixes these errors and you can find it at
>>>> 2d4ee16d969c97996e80e4c9cb6de0acaff22c9f in Linus' tree.
>>>
>>> Thanks for this report, we'll queue it up soon.
>>
>> Odd, that commit is in 6.2 already, so how are you applying this to
>> 6.3.y?
>
> And this is only a gcc13 issue, right? So it's not a regression, it's
> always been there, nothing new caused it in this release from what I can
> tell.
>
> Actually I don't see how this is an issue in 6.3.1 anyway, as again, the
> proposed fix you gave is in 6.2, so what really is happening here?
You seem not to have seen the email I sent shortly after my original report. In that email I apologised for the noise
because, due to a caffeine deficiency, I had reported the problem against the wrong kernel version and that it actually
occurs 6.1.27. gcc13 spits it out as a warning, but kernel build system is setbup to treat warnings as errors, so the
build fails.
Chris
>
> confused,
>
> greg k-h
next prev parent reply other threads:[~2023-05-02 13:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 23:55 Linux 6.3.1 Greg Kroah-Hartman
2023-04-30 23:55 ` Greg Kroah-Hartman
2023-05-01 6:22 ` Chris Clayton
2023-05-01 6:26 ` Chris Clayton
2023-05-01 21:40 ` Greg Kroah-Hartman
2023-05-01 22:28 ` Akemi Yagi
2023-05-01 23:43 ` Greg Kroah-Hartman
2023-05-02 5:07 ` Chris Clayton
2023-05-02 7:31 ` Greg Kroah-Hartman
2023-05-02 13:12 ` Chris Clayton [this message]
2023-05-06 0:52 ` Greg Kroah-Hartman
2023-05-06 10:03 ` Chris Clayton
-- strict thread matches above, loose matches on Subject: below --
2023-05-01 13:03 Ronald Warsow
2023-04-30 23:41 Greg Kroah-Hartman
2023-04-30 23:41 ` Greg Kroah-Hartman
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=c7842e46-fc41-c989-b5e7-ec504cd0c8f2@googlemail.com \
--to=chris2553@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--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