From: piliu <piliu@redhat.com>
To: "HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: makedumpfile: a feature question about filtering
Date: Mon, 14 Sep 2020 12:55:45 +0800 [thread overview]
Message-ID: <0b99591e-7117-7661-e728-684ece22787e@redhat.com> (raw)
In-Reply-To: <OSBPR01MB1991C082928AD18ED5574DDBDD240@OSBPR01MB1991.jpnprd01.prod.outlook.com>
On 09/11/2020 04:53 PM, HAGIO KAZUHITO(萩尾 一仁) wrote:
> Hi Pingfan,
>
> -----Original Message-----
>> Hello,
>>
>> There is an appeal which only wants to save some user page including env
>> and args pages, and discards the other user space pages.
>
> I understand that it's helpful to get them even with -d 31 for crash's
> "ps -a" option..
>
>>
>> To achieve this feature, mm_struct's members "arg_start, arg_end,
>> env_start, env_end;" should be accessed. So we need to export mm_struct
>> and init_mm through vmcore.
>
> How many offsets/sizes will be required to walk all tasks?
At present, I think only the info "arg_start, arg_end, env_start,
env_end" in mm_struct are required.
> If kernel maintainers accept it, I will not oppose that feature..
OK, I will start with kernel side as the first step.
>
> (or it would be simpler to mark the pages something special when allocating,
> but I don't feel like it's easy to change kernel to do so.)
Yes, I agree. From kernel side, the page is a normal user space page,
there should not be exception.
Thanks,
Pingfan
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2020-09-14 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 1:38 makedumpfile: a feature question about filtering piliu
2020-09-11 8:53 ` HAGIO KAZUHITO(萩尾 一仁)
2020-09-14 4:55 ` piliu [this message]
2020-09-14 8:15 ` HAGIO KAZUHITO(萩尾 一仁)
2020-09-14 8:30 ` piliu
2020-09-14 9:15 ` HAGIO KAZUHITO(萩尾 一仁)
2020-09-15 2:30 ` piliu
2020-09-16 8:40 ` HAGIO KAZUHITO(萩尾 一仁)
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=0b99591e-7117-7661-e728-684ece22787e@redhat.com \
--to=piliu@redhat.com \
--cc=k-hagio-ab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox