From: Mike Galbraith <efault@gmx.de>
To: Randy Dunlap <rdunlap@infradead.org>,
Joe Smith <codesoldier1@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: crash binary for latest unreleased kernel
Date: Sat, 27 Jan 2018 05:48:42 +0100 [thread overview]
Message-ID: <1517028522.10239.66.camel@gmx.de> (raw)
In-Reply-To: <b7b94e75-8052-738d-cc18-5aa1d0b4afde@infradead.org>
On Fri, 2018-01-26 at 20:38 -0800, Randy Dunlap wrote:
> 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?
The stuff I've fixed up has been trivial renames and whatnot, operative
word being trivial, easy to find based on gripage. If I don't find it
quickly, I usually decide to not need it _that_ badly, go with plan B.
-Mike
next prev parent reply other threads:[~2018-01-27 4:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 20:52 crash binary for latest unreleased kernel Joe Smith
2018-01-27 4:32 ` Mike Galbraith
2018-01-27 4:38 ` Randy Dunlap
2018-01-27 4:48 ` Mike Galbraith [this message]
2018-01-28 8:37 ` Joe Smith
2018-01-28 9:20 ` Mike Galbraith
2018-01-28 10:00 ` Mike Galbraith
2018-01-28 20:19 ` Joe Smith
2018-01-31 3:51 ` Mike Galbraith
2018-01-31 16:03 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1517028522.10239.66.camel@gmx.de \
--to=efault@gmx.de \
--cc=codesoldier1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox