linux-kernel - Re: pstore to save vmcoreinfo for hypervisors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <1713017371.14449324.1492589994822.JavaMail.zimbra@redhat.com>
Date:   Wed, 19 Apr 2017 04:19:54 -0400 (EDT)
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Marc-André Lureau <marcandre.lureau@...il.com>
Cc:     open list <linux-kernel@...r.kernel.org>, keescook@...omium.org,
        anton@...msg.org, ccross@...roid.com,
        tony luck <tony.luck@...el.com>,
        Ladi Prosek <lprosek@...hat.com>
Subject: Re: pstore to save vmcoreinfo for hypervisors


> It would be interesting to have this information during early kernel boot,
> but which mechanism should be used? pstore seems like an option. There
> could be a new PSTORE_TYPE_VMCOREINFO with the same content as
> /sys/kernel/vmcoreinfo. During boot, the kernel could remove older entries
> if any and add the up to date info (if it detects a VM). qemu or other
> hypervisor could then retrieve it for the dump, likely from an ACPI ERST
> space (EFI var shouldn't be accessed from host according to some
> developpers).

I think that pstore would not be saved by dump-guest-memory in general
(it would with ramoops, but not in general).  I think we need to save
the dump info in an out-of-band channel.

For example, we could have a simple device consisting of a single 4-byte
I/O port, with the following protocol:

- writing zero to the I/O port resets the information

- writing nonzero to the I/O port sets the "type" of the dump information,
  e.g. 1 for Linux vmcoreinfo and 2 for Windows KeInitializeCrashDumpHeader.

- after writing the type, you write the base of the dump header and then
  the length

- if all three values have been written, dump-guest-memory copies the
  data to an ELF note, whose name depends on the "type" value (e.g.
  "VMCOREINFO" for type 1, ".QEMU.WindowsCrashDumpHeader" for type 2).
  The three values are also migrated of course.

The device can be discovered via ACPI like pvpanic.

Paolo