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: <1517133624.6669.22.camel@gmx.de>
Date:   Sun, 28 Jan 2018 11:00:24 +0100
From:   Mike Galbraith <efault@....de>
To:     Joe Smith <codesoldier1@...il.com>
Cc:     Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org
Subject: Re: crash binary for latest unreleased kernel

On Sun, 2018-01-28 at 10:20 +0100, Mike Galbraith wrote:
> On Sun, 2018-01-28 at 00:37 -0800, Joe Smith wrote:
> > I happen to look at the patches for the crash binary and came across
> > this log entry from Jan 19. I am also using 4.15-rc kernel. Not
> > knowing anything about crash it is hard to even attempt to fix it.
> 
> It may not work all that well if box does something new/creative, but
> mundane manual crash, and live rummaging seem to work well enough.

And looking through my modified makedumpfile package, looks like I've
replaced everything I had ever done do it with backports from newer
versions, so you should be able to get kdump working with nothing more
than an update to makefumpfile, plus virgin upstream crash source.

	-Mike