linux-kernel - Re: [PATCH v3 0/4] Remove dependency of check subcmd upon orc

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: <20200730150540.75lm5p5kqdncxpsg@treble>
Date:   Thu, 30 Jul 2020 10:05:40 -0500
From:   Josh Poimboeuf <jpoimboe@...hat.com>
To:     Julien Thierry <jthierry@...hat.com>
Cc:     linux-kernel@...r.kernel.org, peterz@...radead.org, mbenes@...e.cz
Subject: Re: [PATCH v3 0/4] Remove dependency of check subcmd upon orc

On Thu, Jul 30, 2020 at 03:42:09PM +0100, Julien Thierry wrote:
> 
> 
> On 7/30/20 3:06 PM, Josh Poimboeuf wrote:
> > On Thu, Jul 30, 2020 at 10:41:39AM +0100, Julien Thierry wrote:
> > > Hi,
> > > 
> > > Matt Helsley's change[1] provided a base framework to opt-in/out
> > > objtool subcommands at compile time. This makes it easier for
> > > architectures to port objtool, one subcommand at a time.
> > > 
> > > Orc generation relies on the check operation implementation. However,
> > > the way this is done causes the check implementation to depend on the
> > > implementation of orc generation functions to call if orc generation is
> > > requested. This means that in order to implement check subcmd, orc
> > > subcmd also need to be implemented.
> > > 
> > > These patches aim at removing that dependency, having orc subcmd
> > > being built on top of the check subcmd.
> > > 
> > > 
> > > Changes since v2 [2]:
> > > - Rebased on recent tip/objtool/core
> > 
> > tip/objtool/core is slightly outdated, I got a conflict with patch 1.
> > 
> > I guess linus/master would be best.
> 
> It looks like linus/master is missing the rela -> reloc rework that is
> present in tip/objtool/core, which will conflict with other patches from
> this series.
> 
> How shall I proceed?

Hm.  I guess we'll need guidance from Peter, he's the branch wrangler.
Maybe tip/objtool/core needs to be rebased onto linus/master.

-- 
Josh