Thanks for your report.
On Friday, July 6, 2018 7:10 PM, Tetsuo Handa wrote:
> Hello Ken'ichi,
> I noticed that makedumpfile ( https://sourceforge.net/p/makedumpfile/code/ )
> can no longer detect kernel version correctly because "struct uts_namespace"
> (which is exposed to userspace via vmcoreinfo) is subjected to randomization
> by GCC_PLUGIN_RANDSTRUCT kernel config option since 4.13.
> The code was introduced by below commit.
> commit bfc8fe181c822ad0d8495ceda3c7109a407192f0
> Author: ken1_ohmichi <ken1_ohmichi>
> Date: Fri Dec 22 07:41:14 2006 +0000
> linux-2.6.19 support.
> On linux-2.6.18 or former, the release information could be gotten from
> the symbol "system_utsname". But on linux-2.6.19, it can be done from
> symbol "init_uts_ns". A new makedumpfile can get the release information
> from the existing symbol.
> Can you detect kernel version without using "struct uts_namespace" ?
makedumpfile needs a whole "struct new_utsname" data in "struct uts_namespace"
because it has to write the data out to dump file header, so we need to add
the offset of uts_namespace.name to vmcoreinfo or get it from vmlinux.
But I'm not sure whether it is all to get makedumpfile working well with the
randomization, e.g. some additional offset exposures might be needed.
And I saw a report to the crash utility mailing list that crash also couldn't
work with the randomization due to a vmlinux issue, so if it is still not fixed,
even if makedumpfile (and kernel) is fixed, we cannot use crash.
* [Crash-utility] Using crash with structure layout randomized kernel
> On 2018/07/07 1:11, Linus Torvalds wrote:
> > On Fri, Jul 6, 2018 at 3:07 AM Tetsuo Handa
> > <penguin-ker...@i-love.sakura.ne.jp> wrote:
> >> I noticed that makedumpfile utility is failing to check kernel version, for
> >> it depends on offset of "struct uts_namespace"->name being sizeof(int).
> > For something like this, we fix makedumpfile instead. This is not a
> > "user program" using system calls etc, this is something that delves
> > into the kernel dump and tries to make sense of it.
> > Where is the makedumpfile source code? What is it trying to do, and why?
> > One option is to just say "hey, you can't make much sense of a
> > randomized kernel dump anyway, so don't even try".
> > Linus
kexec mailing list