linux-kernel - Re: [PATCH 01/15] liblockdep: Fix undefined symbol prandom

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20170526065444.neuxegeowzvlle5c@gmail.com>
Date:   Fri, 26 May 2017 08:54:44 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     "Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com>
Cc:     "ben@...adent.org.uk" <ben@...adent.org.uk>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 01/15] liblockdep: Fix undefined symbol prandom_u32


* Levin, Alexander (Sasha Levin) <alexander.levin@...izon.com> wrote:

> On Wed, May 24, 2017 at 09:53:37AM +0200, Ingo Molnar wrote:
> > 
> > So I'm not sure how you sent these patches, but probably due to the lack of a 
> > boilerplate message, the order was all mixed up. I got the patch order right on 
> > the third attempt.
> > 
> > But then I encountered this build failure (when applied to Linus's latest tree):
> > 
> > triton:~/tip/tools/lib/lockdep> make
> >   CC       common.o
> >   CC       lockdep.o
> > In file included from lockdep.c:25:0:
> > ../../../kernel/locking/lockdep.c:33:28: fatal error: linux/sched/mm.h: No such 
> > file or directory
> >  #include <linux/sched/mm.h>
> >                             ^
> 
> Heh, apparently a bunch of stuff changed between the point when I sent my
> original pull request and now... I'll resend with additional fixes.

Yeah, and also note that this is v4.13 material at best - liblockdep broke a long 
time ago so it falls under 'development', not 'regression fixes'.

Thanks,

	Ingo