linux-kernel - Re: [PATCH] samsung-laptop: Disable if CONFIG

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]

Date:	Mon, 5 Nov 2012 11:30:31 +0100
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Corentin Chary <corentincj@...aif.net>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Matt Fleming <matt@...sole-pimps.org>,
	Matthew Garrett <mjg@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>, linux-efi@...r.kernel.org,
	"platform-driver-x86@...r.kernel.org" 
	<platform-driver-x86@...r.kernel.org>,
	Alessandro Crismani <alessandro.crismani@...il.com>,
	Mikhail Bakhterev <mike.bakhterev@...il.com>,
	Patrick H <kernel@...storm.net>,
	Matt Fleming <matt.fleming@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>, stable@...r.kernel.org
Subject: Re: [PATCH] samsung-laptop: Disable if CONFIG_EFI=y

On Mon, Nov 05, 2012 at 09:12:01AM +0000, Corentin Chary wrote:
> On Sun, Nov 4, 2012 at 7:37 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> >> Acked-by: Corentin Chary <corentin.chary@...il.com>
> >
> > This is totally bogus and prevents users build a kernel which can work in
> > either mode. As such its a regression.
> 
> Arg.. Sorry for that, I didn't realized that CONFIG_EFI=y was not
> something rare these days.
> 
> > Do the detection check at runtime. If it was booted via EFI then don't
> > grovel in places you shouldn't. Indeed its possible EFI should reserve
> > those memory regions ?
> 
> I wonder how the windows driver works in this case.. Maybe they use
> something completly different, and the SABI interface is still there
> because nobody removed/disabled it ? In this case it's probably not a
> good idea to use it on these machines since the implementation is
> likely to be completly broken.

Odds are, the windows driver just isn't even loaded on the newer
machines, as ACPI works just fine for this.  But, we don't have the
option of shipping custom systems for different laptops like Samsung
does, so we have to probe for this somehow.

Initally we were looking at the DMI strings for specific laptop models,
but that got annoying as we had to keep adding new models.  So we now
just check the memory locations for all Samsung laptops, which was
working fine.

What is the problem if we try to access this memory on UEFI machines?
What is the error that is caused?

Is there any "this_is_a_uefi_system()" type call drivers can make to
just opt-out if that call is true?

thanks,

greg k-h
--
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/