linux-kernel - Re: [PATCH v1 0/2] firmware: dmi_scan: Make it work in kexec'ed kernel

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: <YMeM1Xee9Yg3j21D@smile.fi.intel.com>
Date:   Mon, 14 Jun 2021 20:07:33 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Dave Young <dyoung@...hat.com>
Cc:     Jean Delvare <jdelvare@...e.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Javier Tiá <javier.tia@...il.com>,
        kexec@...ts.infradead.org, Eric Biederman <ebiederm@...ssion.com>,
        linux-efi <linux-efi@...r.kernel.org>,
        Matt Fleming <matt@...eblueprint.co.uk>,
        Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [PATCH v1 0/2] firmware: dmi_scan: Make it work in kexec'ed
 kernel

On Mon, Jun 14, 2021 at 06:38:30PM +0300, Andy Shevchenko wrote:
> On Sat, Jun 12, 2021 at 12:40:57PM +0800, Dave Young wrote:
> > > Probably it is doable to have kexec on 32bit efi working
> > > without runtime service support, that means no need the trick of fixed
> > > mapping.
> > > 
> > > If I can restore my vm to boot 32bit efi on this weekend then I may provide some draft
> > > patches for test.
> > 
> > Unfortunately I failed to setup a 32bit efi guest,  here are some
> > untested draft patches, please have a try.
> 
> Thanks for the patches.
> 
> As previously, I have reverted my hacks and applied your patches (also I
> dropped patches from previous mail against kernel and kexec-tools) for both
> kernel and user space on first and second environments.
> 
> It does NOT solve the issue.
> 
> If there is no idea pops up soon, I'm going to resend my series that
> workarounds the issue.

Hold on, I may have made a mistake during testing. Let me retest this.

-- 
With Best Regards,
Andy Shevchenko