linux-kernel - Re: crash binary for latest unreleased kernel

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: <b7b94e75-8052-738d-cc18-5aa1d0b4afde@infradead.org>
Date:   Fri, 26 Jan 2018 20:38:51 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Mike Galbraith <efault@....de>, Joe Smith <codesoldier1@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: crash binary for latest unreleased kernel

On 01/26/2018 08:32 PM, Mike Galbraith wrote:
> On Fri, 2018-01-26 at 12:52 -0800, Joe Smith wrote:
>> Hi,
>>
>> I am doing development on the latest unreleased kernel on a system
>> running ubuntu 16.04. I can not get crash dump to be saved or use
>> crash on the live system. I have tried compiling crash on the system.
>>
>> What is the trick to do development on the latest kernel using a
>> system installed with old release.
> 
> You have to either be motivated enough to fix crash and friends up as
> they get busted, or lazy enough to wait for maintainers to do so for
> you.  I've done a bit of both, but the later is my favorite :)

:)

Is it mostly structure updates or is it partly randomized layout of
structs?  or something totally different?

thanks,
-- 
~Randy