linux-kernel - Re: [PATCH 1/2] Make efifb check that the base address is plausible on pci systems.

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, 13 Sep 2010 10:42:27 -0400
From:	Peter Jones <pjones@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	linux-fbdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] Make efifb check that the base address is plausible
 on pci systems.

On 09/10/2010 08:14 PM, Andrew Morton wrote:
> On Thu,  9 Sep 2010 15:16:48 -0400
> Peter Jones <pjones@...hat.com> wrote:
> 
>> Some Apple machines have identical DMI data but different memory
>> configurations for the video. Given that, check that the address in our
>> table is actually within the range of a PCI BAR on a VGA deivce in the
>> machine.
>>
>> This also fixes up the return value from set_system(), which has
>> always been wrong, but never resulted in bad behavior since there's only
>> ever been one matching entry in the dmi table.
>>
>> This also adds me as the efifb maintainer, since I've effectively been
>> acting as such for quite some time.
> 
> And what is the impact (and importance) of this patch?  Make some
> people's Mac displays work, I'd be guessing?
> 

That's correct.

-- 
        Peter

Gravity is a habit that is hard to shake off.
		-- Pratchett

01234567890123456789012345678901234567890123456789012345678901234567890123456789
--
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/