linux-kernel - Re: [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHD1Q_zk6Z841E1yAH-GKpDXQ=32YPb-R4Exo7UcNHnTY3bdqQ@mail.gmail.com>
Date:   Mon, 16 Nov 2020 18:49:08 -0300
From:   Guilherme Piccoli <gpiccoli@...onical.com>
To:     "Eric W. Biederman" <ebiederm@...ssion.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Bjorn Helgaas <helgaas@...nel.org>, lukas@...ner.de,
        linux-pci@...r.kernel.org, Pingfan Liu <kernelfans@...il.com>,
        andi@...stfloor.org, "H. Peter Anvin" <hpa@...or.com>,
        Baoquan He <bhe@...hat.com>, x86@...nel.org,
        Sinan Kaya <okaya@...nel.org>, Ingo Molnar <mingo@...hat.com>,
        Jay Vosburgh <jay.vosburgh@...onical.com>,
        Dave Young <dyoung@...hat.com>,
        Gavin Guo <gavin.guo@...onical.com>,
        Borislav Petkov <bp@...en8.de>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Guowen Shan <gshan@...hat.com>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        "Guilherme G. Piccoli" <kernel@...ccoli.net>,
        kexec mailing list <kexec@...ts.infradead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Dan Streetman <ddstreet@...onical.com>,
        Vivek Goyal <vgoyal@...hat.com>
Subject: Re: [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks

On Mon, Nov 16, 2020 at 6:45 PM Eric W. Biederman <ebiederm@...ssion.com> wrote:
> The way to do that would be to collect the set of pci devices when the
> kexec on panic kernel is loaded, not during crash_kexec.  If someone
> performs a device hotplug they would need to reload the kexec on panic
> kernel.
>
> I am not necessarily endorsing that just pointing out how it can be
> done.
>
> Eric

Thanks Eric, I agree! I think if we use something like PKRAM (a more
dynamic approach) we could have the PCI hotplug path updating the data
to-be-passed to the crash kernel, so the crash kernel doesn't even
need to be loaded again.