linux-kernel - Re: linux-next: build failure after merge of the integrity 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] [day] [month] [year] [list]

Message-Id: <1565118136.11223.215.camel@linux.ibm.com>
Date:   Tue, 06 Aug 2019 15:02:16 -0400
From:   Mimi Zohar <zohar@...ux.ibm.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Thiago Jung Bauermann <bauerman@...ux.ibm.com>
Cc:     Mimi Zohar <zohar@...ux.vnet.ibm.com>,
        Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Philipp Rudo <prudo@...ux.ibm.com>,
        Jessica Yu <jeyu@...nel.org>
Subject: Re: linux-next: build failure after merge of the integrity tree

Hi Stephen,

On Tue, 2019-08-06 at 13:45 +1000, Stephen Rothwell wrote:
> Hi Thiago,
> 
> On Tue, 06 Aug 2019 00:18:06 -0300 Thiago Jung Bauermann <bauerman@...ux.ibm.com> wrote:
> >
> > Sorry for the trouble. I wasn't aware of that build time check.
> > I'll enable HEADER_TEST and KERNEL_HEADER_TEST for my next patches.

ditto

> 
> I do allmodconfig builds which enable those.
> 
> > Thanks for providing the fix. Should I post a new version or can Mimi
> > squash the above into the original patch?
> 
> Up to Mimi, but either works (or just committing my patch if the tree is
> normally not rebased).

Based on the new "Documentation/maintainer/rebasing-and-merging.rst",
I'm under the impression that we shouldn't be rebasing, even for
"just" adding tags.  Waiting for tags before pushing out to next-
integrity is causing delays, but we're trying out this approach.  So
for now, I've included your commit.

thanks,

Mimi