All of lore.kernel.org
 help / color / mirror / Atom feed
From: Louis Bouchard <louis.bouchard@canonical.com>
To: Atsushi Kumagai <ats-kumagai@wm.jp.nec.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: makedumpfile-1.5.9: Introduce parallel compression processing.
Date: Fri, 20 Nov 2015 11:22:53 +0100	[thread overview]
Message-ID: <564EF47D.7090202@canonical.com> (raw)
In-Reply-To: <0910DD04CBD6DE4193FCF86B9C00BE9701E059DD@BPXM01GP.gisp.nec.co.jp>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello Kumagai-san,

Le 19/11/2015 08:30, Atsushi Kumagai a écrit :
> Hello Louis,
> 
>>>>> o Support new kernels - The supported kernel is updated to 4.1 in
>>>>> this version. At first I'm going to extend the supported version to
>>>>> 4.2, but I found an issue that makedumpfile seems to exclude
>>>>> necessary pages by mistake on linux 4.2. When crash-7.1.3 reads
>>>>> that filtered dump file, the following message is shown.
>>>>> 
>>>>> crash: page excluded: kernel virtual address: f3fe0000  type:
>>>>> "fill_task_struct"
>>>>> 
>>>>> This will be fixed in the next version.
>>>> 
>>>> Have you fixed the 4.2 kernel issue already or you intend to work on
>>>> it in the future ?
>>> 
>>> I haven't done anything yet, I was going to work from now.
>>> 
>>>> Both Debian and Ubuntu run 4.2 kernel so if waiting for a fix is
>>>> acceptable I would rather bring in a 1.5.9 + patch version.
>>> 
>>> So it will be helpful if you can do it.
>>> 
>>> 
>>> Thanks, Atsushi Kumagai
>>> 
>> 
>> That is perfect.  Just let me know once you have identified a fix and I
>> will include it in the new package.
> 
> I confirmed that there is no problem in makedumpfile, so you don't need to 
> update your makedumpfile packages.
> 
> That was a crash side issue and the problem is still under discussion. The
> warning I reported first is going to be solved in the next crash version, 
> but "struct" and "task" commands with task_struct (or some corresponding
> fields) can fail if a dumpfile of linux 4.2 is filtered.
> 
> You should see this thread for more details:
> 
> https://www.redhat.com/archives/crash-utility/2015-November/msg00021.html
> 
> 
> Thanks, Atsushi Kumagai
> 

As I understand it, 1.5.9 will work fine on 4.2 kernels.  But as the released
source stand, 1.5.9 only supports up to 4.1.  Should I simply go ahead and
"manually" add support statement for 4.2 (in README & makedumpfile.h) or you
prefer to change it in your git tree ?

Kind regards,

...Louis

- -- 
Louis Bouchard
Software engineer, Cloud & Sustaining eng.
Canonical Ltd
Ubuntu developer                       Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63  B9C4 8B3D 867C 823E 7A61
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWTvR9AAoJEFZStL2qfwOthLEP/A042ORfYD6vfKTM7WWjW5Yh
upEkZQKms7I2HzGGWhC1x1TtJAmvWOK8G7Vou+ULpKMjH8byRMivP7ioTSqtw24J
aTiwLiC+2K2QleasjeYtY5pY3OOyhIsd7XOIxfcvuPa46ssmsGevnq6ZFB06s5nx
HrkfYQRuT6uLQRqpem61N8gykngABJ25b7REGYhjsSl0OZNwz1YBlpHtQqgEXtm2
Cr17q2yTyV8t05LgQ35JMEoIRbgw4bKobMhV2yP0HnZjHyXVoeEY4VhBwU9Aor4A
laycOk5u0bShqEIoeweBSdW+2qMld2kM/y3uGABOpByZgQSmNVtmBzXaMPPHELRd
XtghNxOPvRLa5ukw6ebBI+fRMuxxd6K/OpmEk2p2fVlfBxBwFHQSQy+lp9WBKF/r
ZDPiIXq1xYlNS5eGQcAXsT+48jaR656rxkuEv5RQoNNMv/KVS2l0KtE10umfTjJY
72A2g240gRzSIQzBwUaheKC/FDBRjL2NETTNvnU3iGWMdctAsKd3kck5CKIooPX5
CUVeMndqEenfWMrOjLGsfWJpwW+vHMI0Q0wGUn/RMk733r34rZYHN3m86Ph2cRAh
RLQYONyDQGp1ig4KKmTwkOgKIoR7vbeWqbOeg3jMaO8VNDJXUmRQYEGfzf3bamcK
g0txtgExdvXsvgoeAHri
=Dv4d
-----END PGP SIGNATURE-----

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2015-11-20 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  6:31 makedumpfile-1.5.9: Introduce parallel compression processing Atsushi Kumagai
2015-10-28  8:23 ` Louis Bouchard
2015-10-28  9:07   ` Atsushi Kumagai
2015-10-28  9:49     ` Louis Bouchard
2015-11-19  7:30       ` Atsushi Kumagai
2015-11-20 10:22         ` Louis Bouchard [this message]
2015-11-24  2:48           ` Atsushi Kumagai

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=564EF47D.7090202@canonical.com \
    --to=louis.bouchard@canonical.com \
    --cc=ats-kumagai@wm.jp.nec.com \
    --cc=kexec@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.