linux-kernel - Re: [PATCH 0/3] Early use of boot service memory

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: <20131114014043.GD25344@anatevka.fc.hp.com>
Date:	Wed, 13 Nov 2013 18:40:43 -0700
From:	jerry.hoemann@...com
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	rob@...dley.net, tglx@...utronix.de, mingo@...hat.com,
	x86@...nel.org, matt.fleming@...el.com, yinghai@...nel.org,
	penberg@...nel.org, akpm@...ux-foundation.org,
	linux-doc@...r.kernel.org, linux-efi@...r.kernel.org,
	vgoyal@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Early use of boot service memory

On Wed, Nov 13, 2013 at 04:05:50PM -0800, H. Peter Anvin wrote:
> On 11/13/2013 03:57 PM, jerry.hoemann@...com wrote:
> > 
> > I think i can go to a date based black list, that removes the manual
> > step.  System running firmware before certain date assumes we need
> > to do the work around.  If firmware is newer than that date, we don't
> > use the workaround.  Blacklist overrides and allows current behavior
> > for new firmware that is subsequently found to be broken and for
> > which we can't convenience the manufacturer to fix.
> > 
> 
> No, we can't, at least not for now.  We are continually finding new
> platforms with the bug.

  Does you have a list of systems that require efi_reserve_boot_services?
  might be useful from a testing standpoint to get access to one.


> 
> > 
> > I will still point out that as currently used, efi_reserve_boot_services
> > is wrong.  A work around for firmware bugs on one platform shouldn't be
> > breaking platforms that don't have that bug.  Its just much less likely
> > to cause problems with higher crash kernel allocation.
> > 
> 
> It is wrong, yes, but it seems like a ubiquitous problem.
> 
> 	-hpa

-- 

----------------------------------------------------------------------------
Jerry Hoemann            Software Engineer              Hewlett-Packard/MODL

3404 E Harmony Rd. MS 57                        phone:  (970) 898-1022
Ft. Collins, CO 80528                           FAX:    (970) 898-XXXX
                                                email:  jerry.hoemann@...com
----------------------------------------------------------------------------

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/