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: <CABGNeczUC8nt3PYSjSRUr-j_sxEA=k9cbwBaygA=WPwq-3jLFQ@mail.gmail.com>
Date:   Sun, 28 Jan 2018 12:19:18 -0800
From:   Joe Smith <codesoldier1@...il.com>
To:     Mike Galbraith <efault@....de>
Cc:     Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org
Subject: Re: crash binary for latest unreleased kernel

Thanks a lot, Mike. Following your suggestions worked !!!!

Regards,

On Sun, Jan 28, 2018 at 2:00 AM, Mike Galbraith <efault@....de> wrote:
> 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



-- 
JS