linux-kernel - Re: linux-next: build failure after merge of the v9fs tree

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]

Date:   Mon, 05 Dec 2022 21:40:06 +0100
From:   Christian Schoenebeck <linux_oss@...debyte.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Dominique Martinet <asmadeus@...ewreck.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the v9fs tree

On Monday, December 5, 2022 3:31:57 PM CET Christian Schoenebeck wrote:
> On Monday, December 5, 2022 5:10:18 AM CET Dominique Martinet wrote:
> > Stephen Rothwell wrote on Mon, Dec 05, 2022 at 03:03:16PM +1100:
> > > After merging the v9fs tree, today's linux-next build (i386 defconfig)
> 
> > > failed like this:
> [...]
> 
> > > net/9p/client.c:523:17: note: in expansion of macro 'pr_err'
> > > 
> > >   523 |                 pr_err(
> > >   
> > >       |                 ^~~~~~
> > > 
> > > cc1: all warnings being treated as errors
> > > 
> > > Caused by commit
> > > 
> > >   36cd2f80abf8 ("net/9p: fix response size check in p9_check_errors()")
> > > 
> > > I have applied the following patch for today:
> > Thank you!
> > I guess I should start building one 32bit kernel somewhere...
> :
> :/ I'll setup a 32-bit build system as well, sorry!

Dominique, looking at your 9p queue, I just realized what happened here: I 
posted a v2 of these two patches, which got lost for some reason:

https://lore.kernel.org/all/cover.1669144861.git.linux_oss@crudebyte.com/

The currently queued 1st patch is still v1 as well.

Best regards,
Christian Schoenebeck