Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Egorenkov <egorenar@linux.ibm.com>
To: "HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: RE: [PATCH v2 1/1] Calculate offset to field 'init_uts_ns.name'
Date: Thu, 17 Sep 2020 18:32:23 +0200	[thread overview]
Message-ID: <87mu1o1i08.fsf@oc8242746057.ibm.com> (raw)
In-Reply-To: <OSBPR01MB199111D24037A49B136EBF76DD3E0@OSBPR01MB1991.jpnprd01.prod.outlook.com>

HAGIO KAZUHITO(萩尾 一仁)	<k-hagio-ab@nec.com> writes:

>
> Thank you for catching this and the patch.
>
> but do you know the kernel patch corresponding to this patch, i.e. adds
> the OFFSET(init_uts_ns.name) (strictly, OFFSET(uts_namespace.name) probably)
> entry to vmcoreinfo?  The makedumpfile usually just read it from vmcore,
> so cannot calculate without debug info in vmlinux.
>
> If it has not been posted yet, we need to do.  The best situation is
> that the patch is merged into linux-next first and then merged into
> mainline together with the commit 9a56493f6942.
>
> Is it possible for you?  otherwise, anyone or I might try.
>

Hi Kazu,

my patch doesn't really work :( The offset from 'init_uts_ns' to 'name'
has changed from 4 to 0 but how do you handle that in makedumpfile w/o
first knowing what kernel version that is. It is a chicken-and-egg
problem. Not sure how to solve it. The Linux kernel doesn't provide
the symbol 'init_ns_ns.name' as i initially thought and ,therefore,
i based my patch on a wrong assumption. It would be nice if kernel just
provided a symbol for 'init_uts_ns.name' instead of 'init_uts_ns' which
might change anytime.

Regards
Alex

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

  parent reply	other threads:[~2020-09-17 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 13:51 [PATCH v2 1/1] Calculate offset to field 'init_uts_ns.name' Alexander Egorenkov
2020-09-17  5:34 ` HAGIO KAZUHITO(萩尾 一仁)
2020-09-17 11:03   ` Alexander Egorenkov
2020-09-17 16:32   ` Alexander Egorenkov [this message]
2020-09-18  2:23     ` 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=87mu1o1i08.fsf@oc8242746057.ibm.com \
    --to=egorenar@linux.ibm.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