linux-kernel - Re: linux-next: build failure after merge of the xfs 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]

Message-ID: <20191029172351.40eae30d@canb.auug.org.au>
Date:   Tue, 29 Oct 2019 17:23:51 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Christoph Hellwig <hch@....de>
Cc:     "Darrick J. Wong" <darrick.wong@...cle.com>,
        David Chinner <david@...morbit.com>, linux-xfs@...r.kernel.org,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the xfs tree

Hi Christoph,

On Tue, 29 Oct 2019 06:56:05 +0100 Christoph Hellwig <hch@....de> wrote:
>
> On Mon, Oct 28, 2019 at 04:18:06PM -0700, Darrick J. Wong wrote:
> > On Tue, Oct 29, 2019 at 10:11:51AM +1100, Stephen Rothwell wrote:  
> > > Hi all,
> > > 
> > > After merging the xfs tree, today's linux-next build (powerpc
> > > ppc64_defconfig) failed like this:  
> > 
> > <groan> Yeah, that's the same thing reported by the kbuild robot an hour
> > ago.  FWIW I pushed a fixed branch but I guess it's too late for today,
> > oh well....
> > 
> > ...the root cause of course was the stray '}' in one of the commits,
> > that I didn't catch because compat ioctls are hard. :(  
> 
> Weird.  My usual builds have compat ioclts enabled, and I never got
> any report like this.

It only fails for !(defined(CONFIG_IA64) || defined(CONFIG_X86_64))
I reported it failing in my powerpc build.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped