linux-kernel - Re: Linux 6.3.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2023050201-bluish-habitable-474a@gregkh>
Date:   Tue, 2 May 2023 16:31:56 +0900
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Chris Clayton <chris2553@...glemail.com>
Cc:     linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
        torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
        jslaby@...e.cz
Subject: Re: Linux 6.3.1

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?

confused,

greg k-h